I believe when Jes switches to procxx then back to PROC00 it
will re-allocate all the proclibs which should pick up the new location
of lib03.  I switched to dynamic procs awhile ago so I can't test it
myself.   Should be easy enough to check though - run a typrun=scan that
has a proc unique to lib03 which should cause the error,  in the same
initiator run the iefbr14 switching procxx,  then again in same init
re-run the typrun=scan and hopefully the error should be gone.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Vernooy, C.P. - SPLXM
Sent: Wednesday, February 08, 2006 9:07 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JES2 proclibs allocated???

David,

I remember your trick, but do not recall what it was for. It causes JES2
to close PROC00 and open PROC01 for this particular job and will switch
back to PROC00 for the next job that does not specify a //PROCLIB.

I don't see how this helps in this situation. PROCLIBs are used by the
convertor, which run in JES2 address space, that is why this DD
statement is in JES2 JCL. lib03 remains in the PROC00 concatenation and
will be searched if a PROC is not found in lib01 and lib02 and will keep
on giving 213-04 abends.

Kees.

"Clark, David" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
>       It's been awhile, but it seems like I remember this could be
> fixed by switching the proc list - run an iefbr14 job with
>
> /*JOBPARM      PROCLIB=PROC01
>
>       You'll need to run it in each initiator is the down side.  Be a
> real pain if there's many defined and probably easier to hot start Jes
> as others suggested.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
> Behalf Of Christian Blesa
> Sent: Wednesday, February 08, 2006 8:07 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: JES2 proclibs allocated???
>
> Hello,
>
> at following scenario:
>
> //PROC00   DD DISP=SHR,DSN=lib01
> //         DD DISP=SHR,DSN=lib02
> //         DD DISP=SHR,DSN=lib03
>
> 1) TDMF process have moved lib03 to another DASD.
> 2) This lib03 has been deleted (manually).
> 3) This lib03 has been allocated (through 3.2 option) from system "x"
>
> Then, some messages are showed:
> IEC143I 213-04,xxxxxxxx,JES2,JES2,PROC00-0003,uuuu,volser
>
> How could fix it?
>
> Regards
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to