MVSFORUMS.com

[Sreejith]

All,
I have a CLIST application using ISPF panels and will submit certain JCLs depending on the options selected. These JCLs use PROCS and I want to change PROC library if it is submitted from a TEST system. I know this can be done by changing the JCL and point it to a different PROC library.

But is there a way in CLIST to do this ? something like follwing for a JCL PROC library ?

[expat]

Yes, there is.

I assume that your JCL is generated using skeletons, ISPSLIB members

If you use a JCLLIB statement as show below,

// JCLLIB ORDER=(&JCLLIB)

You can set the variable to reflect the PROC library depending on whatever it is you want it to depend on.

CLIST .......................................
REXX is so so much easier
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?

[expat]

Or you could LIBDEF the ISPSLIB
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?

[Sreejith]

expat,
Thanks for the reply. I am aware of the JCLLIB ORDER. But there are 100's of JCLs in this application and I will keep this (adding JCLLIB ORDER) as my last option. I will try ISPSLIB. I did a QW on LIBDEF and it didn't suggest that we can use ISPSLIB as PROC Library. But I don't know much about CLISTs and I will give it a try.

Thanks
Sreejith

[semigeezer]

You have to change the JCL. The way the job runs has nothing to do with any settings in your TSO (ISPF) Session.

It sounds like your JCL already exists, that you are not generating it with skeletons. If that is true, then the easiest way to do this is to create a copy of the JCL you will be submitting into a temporary data set, run the EDIT service with an initial macro, and have the edit macro change or add the JCLLIB statement as needed. Then submit and delete the temporary data set.

Assuming that the JCL has only one job per file (member), the edit macro should be only a few lines long. Basically, see if the JCLLIB is there, and replace it, or add it after the job card. The hardest part is insuring that you add it in the right place because the job card can be any number of statements. But that is only a few lines of code too.

[Sreejith]

semigeezer,
Thanks. I still think there could be a way using CLIST itself. How does JES know where to look for the PROC ? This is defined some where ?. I am guessing this is defined using the logon PROC. I am hoping to do the same thru clist.

Thanks
Sreejith

[semigeezer]

It has nothing to do with your TSO session. Your TSO session is just another job in the system. JES knows where to look because of the way JES was configured (through a DD statement in the JCL that started JES).

I think you are thinking that the job you are submitting is somehow running within your TSO session. It is not. Once you send the job to JES via the submit command or other means (intrdr, ftp, etc), JES interprets the JCL. It then creates a whole new address space, completely independent of other address spaces in the system (well, technically there is an initiator address space as a parent). That is what MVS is all about - multiple virtual systems - each job, TSO user, and CICS region, system address space, etc gets its own image of the system resources. I'd suggest reading a little about jobs and address spaces. I think you'll find it interesting and useful.

[Sreejith]

semigeezer,
Thanks for your reply. this is a pretty good insight for me into JES.

Thanks
Sreejith