Using different values for Skeleton dialog variables in loop

venksiv · New User Joined: 20 Jun 2015 Posts: 26 Location: INDIA

Hi all,

I am using )DO loop in JCL skeleton to create multiple DB2 BIND steps. I have generated different values for dialog variable (say, OWNER) in the REXX EXEC as shown below:
OWNER1 = TGAWTBT
OWNER2 = TGBWTBT
and so on..

I also figured to manipulate the dialog variable to be used in the skeleton (like STEP name below). But I am getting "OWNER1" in the output whereas I intend to get "TGAWTBT".

I refered the below URL from our forum (in addition to many others).
job Step to be run n number of times changing sysin card
However, I need to have a different values in place of "PART1" or "PART2" of the SYSIN card output.

I have been instructed to have only one Skeleton JCL. So, I can't loop the FTINCL command for this step, generate multiple parts and then club them to form a single JCL.

Skeleton:

don.leahy · Posted: Thu Sep 03, 2015 5:57 pm

If I were faced with this, I would set up the function that invokes FTINCL to store the list of OWNERs in an ISPF table.

Then I would use the )DOT ...)ENDDOT skeleton commands to tailor JCL for each OWNER in the table.

venksiv · New User Joined: 20 Jun 2015 Posts: 26 Location: INDIA

Thank you for your reply, don.leahy!

I am referring to the documentation at
Control Statements

I will achieve it with a little explanation on how this works. Could you please help me?[/url]

don.leahy · Posted: Thu Sep 03, 2015 6:19 pm

I suggest that you also read up on ISPF Tables. These tables, not to be confused with DB2 tables, are easy to set up and use. Most of the time they are temporary in nature and are deleted when the dialog completes.

My suggestion is that you change the function (easy if it is Rexx) that invokes FTINCL. Use TBCREATE service to create the ISPF table, and then the TBADD service to add a row for each value of &OWNER.

In the skeleton, use the )DOT control statement. )DOT means 'DO Table' and has actually been available longer than the )DO statement. )DOT table_name causes file tailoring to loop through each row in the table, tailoring the skeleton JCL that appears between the )DOT and )ENDDOT statements.

Mickeydusaor · Posted: Thu Sep 03, 2015 7:28 pm

you have several ways of doing this.

change the following to
1. SET TEMP1 = OWNER&SNUM change to SET TEMP1 = OWNER.&SNUM

2. BIND OWNER (OWNER1) change to BIND OWNER (&OWNER.&SNUM)

venksiv · New User Joined: 20 Jun 2015 Posts: 26 Location: INDIA

Hi Don,

Great suggestion! After reading your post and re-reading the other post I referenced in my initial message, I realize that I haven't properly read the reference. I tried the sample code using ISPF Table and )DOT which Pandora-Box had shared. It's working perfectly and seems to be the solution I am looking for.

Hi Mickeydusaor,

I tried your suggestion in my code. I got the text "&OWNER1" instead of the value "TGAWTBT" I expected there. To be more precise, I got the variable name instead of the value I have in the EXEC.

New result:

venksiv · New User Joined: 20 Jun 2015 Posts: 26 Location: INDIA

Hi all,

I tried )DOT concept. Unfortunately, this works only for the looping part. Meaning, JCL is tailored correctly if this (bind) is the only step in the skeleton. I am getting ISPG117 error with abend code of ISPFILTR if I have other steps in the same skeleton.

I am not sure about how to fix this issue using this reference post. I need the JCL in a PDS after I execute the job but this post deals with only ZTEMPF.

I need to have other steps in the same job that would execute once, like load module and DBRM copy steps as depicted below:

venksiv · New User Joined: 20 Jun 2015 Posts: 26 Location: INDIA

Issue resolved!!

The issue (message ISPG117 with abend code = ISPFILTR) occurred while operating on other skeletons (control card for constructing email text) between the ISPF table creation and the JCL skeleton [that contained )DOT]. When I placed the segment of code that constructs multiple steps using )DOT section of Skeleton immediately after the ISPF table creation the issue got resolved. It smoothly operated on the other skeletons after creating the JCL.

Logically, I will first create the JCL and then create the control cards. If both are successful, i will submit the job which solves the purpose. This way the dynamic JCL creation with dynamic values worked fine.

REXX EXEC:

venksiv · New User Joined: 20 Jun 2015 Posts: 26 Location: INDIA

Please be informed that I have removed certain JCL statements (DD statements) in the skeleton and result. Please have all JCL statements in case you wish to construct JCL for processing. I intended to post the working logic.