Changes in TSO SYSEXEC concat

2007-09-23 Thread R.S.
I just added a member to PDS on SYSEXEC concatenation. Unfortunately I can't use 'TSO membername' command. I get IKJ56500I COMMAND membername NOT FOUND. Any clue ? -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sąd Rejonowy dla m. st. Warsza

Re: Changes in TSO SYSEXEC concat

2007-09-23 Thread Mark Jacobs
R.S. wrote: I just added a member to PDS on SYSEXEC concatenation. Unfortunately I can't use 'TSO membername' command. I get IKJ56500I COMMAND membername NOT FOUND. Any clue ? Is the library being managed by VLF? -- Mark Jacobs Time Customer Service Tampa, FL -- Pound pastrami, can kr

Re: Changes in TSO SYSEXEC concat

2007-09-23 Thread Chris Mason
updated rather than being added, was to compress the partitioned data set. Chris Mason - Original Message - From: "R.S." <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: Sent: Sunday, September 23, 2007 9:35 AM Subject: Changes in TSO SYSEXEC concat I just a

Re: Changes in TSO SYSEXEC concat

2007-09-23 Thread Mark Zelden
On Sun, 23 Sep 2007 04:02:24 -0400, Mark Jacobs <[EMAIL PROTECTED]> wrote: >R.S. wrote: >> I just added a member to PDS on SYSEXEC concatenation. Unfortunately I >> can't use 'TSO membername' command. >> I get IKJ56500I COMMAND membername NOT FOUND. >> >> Any clue ? >> >Is the library being manage

Re: Changes in TSO SYSEXEC concat

2007-09-23 Thread Eric Bielefeld
I don't think anyone mentioned it, but try a refresh of LLA. We had some of our main ISPF clist and panel libraries in LLA, and when you added a new member or updated a member, you couldn't access the new or updated member until you did the refresh of LLA. That problem still bit me years after

Re: Changes in TSO SYSEXEC concat

2007-09-23 Thread Walt Farrell
> FYI... taking additional extents with SYSEXEC would NOT cause this problem. Even with the default of EXECUTIL EXECDD(NOCLOSE) in effect? -- Walt -- For IBM-MAIN subscribe / signoff / archive access instructions, send email

Re: Changes in TSO SYSEXEC concat

2007-09-23 Thread R.S.
Mark Jacobs wrote: R.S. wrote: I just added a member to PDS on SYSEXEC concatenation. Unfortunately I can't use 'TSO membername' command. I get IKJ56500I COMMAND membername NOT FOUND. Any clue ? Is the library being managed by VLF? No, it's not, however what are the steps for VLF managed l

Re: Changes in TSO SYSEXEC concat

2007-09-24 Thread Jack Hofbauer
-MAIN@BAMA.UA.EDU Objet : Changes in TSO SYSEXEC concat I just added a member to PDS on SYSEXEC concatenation. Unfortunately I can't use 'TSO membername' command. I get IKJ56500I COMMAND membername NOT FOUND. Any clue ? -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorsk

Re: Changes in TSO SYSEXEC concat

2007-09-24 Thread Mark Zelden
On Sun, 23 Sep 2007 15:00:18 -0500, Walt Farrell <[EMAIL PROTECTED]> wrote: >> FYI... taking additional extents with SYSEXEC would NOT cause this problem. > >Even with the default of EXECUTIL EXECDD(NOCLOSE) in effect? Yes. Even though that is the default, I did purposely set it and tested to

Re: Changes in TSO SYSEXEC concat

2007-10-01 Thread Shmuel Metz (Seymour J.)
In <[EMAIL PROTECTED]>, on 09/23/2007 at 09:35 AM, "R.S." <[EMAIL PROTECTED]> said: >Any clue ? Apparently not your problem, but sometimes that's the result of putting a CLIST in SYSEXEC rather than in SYSPROC. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see