开云体育

I want to add the SYSCPK to my VS1.

My first hurdle is the PROCLIB. On MVS, you can add a PROCLIB by changing the PROC that runs JES2.

Near as I can tell, on VS1, I would need to add all the PROCs to SYS1.PROCLIB.

Is that the case or am I missing something?

On Wed, Jul 5, 2023 at 05:14 AM, Doug Wegscheid wrote:

My first hurdle is the PROCLIB. On MVS, you can add a PROCLIB by changing the
PROC that runs JES2.

Near as I can tell, on VS1, I would need to add all the PROCs to SYS1.PROCLIB.

Well, what task using the PROCLIB, the reader or the initiator? (Who allocates it?)

On Wed, Jul 5, 2023 at 01:40 PM, Drew Derbyshire wrote:

Well, what task using the PROCLIB, the reader or the initiator? (Who allocates it?)

A good question, I see where you were steering me, thanks!

Neither the proc for the RDR nor the INIT has a DD for any proclib.

On Wed, Jul 5, 2023 at 01:40 PM, Drew Derbyshire wrote:

Well, what task using the PROCLIB, the reader or the initiator? (Who allocates it?)

ok, you asked the right question.

from PDF page 147/document page PRO 9.

"Your procedure for the reader can include a DD statement that defines the procedure library."

//IEFPDSI DD .......

Adding user proclibs in VS1 is kind of messy.

There is a "default" proclib defined for VS1 use. If a reader is started by a STARTF command, or if the RDR proc doesn't contain an IEFPDSI DD statement, that "default" proclib is what is used to resolve procedure references in JCL. In VS1 releases 6.7 and earlier, that "default" proclib can't be modified by the user, and is always SYS1.PROCLIB. So the answer is, yes, you have to put your procs in SYS1.PROCLIB unless you want to add a user proclib, and the only way to specify a user proclib is to start a RDR proc that has an IEFPDSI DD statement defining your proclibs (you can't use the STARTF command and get a user proclib). For example, you would modify the RDR proc to add IEFPDSI DD statements defining the proclibs:

//IEFPDSI DD DSN=SYS1.PROCLIB,DISP=SHR,DSN=BLKSIZE=19040
// DD DSN=SYS2.PROCLIB,DISP=SHR

and then start your reader using a:

S RDR,00C

command instead of a STARTF.

--

On Sat, Jul 8, 2023 at 01:17 PM, Kevin Leonard wrote:

For example, you would modify the RDR proc to add IEFPDSI DD statements defining the proclibs:

//IEFPDSI DD DSN=SYS1.PROCLIB,DISP=SHR,DSN=BLKSIZE=19040 // DD DSN=SYS2.PROCLIB,DISP=SHR

and then start your reader using a:

S RDR,00C

command instead of a STARTF.

that's what I ended up doing, works great.

I'm working on a script to take SYSC.PROCLIB and produce SYSC.PROCVS1 (no SYSOUT=*, no VIO). I should have it all packaged up in a week or so.