IF/THEN/ELSE for JCL Steplib

MurthyJ · New User Joined: 12 Mar 2008 Posts: 2 Location: hyd

Hi Friends,

Can we use IF/THEN/ELSE conditions as follows,IF
SO can you please provide me an example...

//STEP1 TO READ A FILE
(The file will have a single value either 1 or 0)
//STEP2 EXEC PGM=P1
//IF FILE.VALUE = 1 THEN
//STEPLIB DD DSN=LOAD1 LIBRARY
//ELSE
//STEPLIB DD DSN=LOAD2 LIBRARY
//ENDIF

Its really appreciable.

dick scherrer · Posted: Thu May 01, 2008 7:31 am Post subject:

Hello,

Sorry, no.

jsathishbabu84 · New User Joined: 07 Jun 2007 Posts: 17 Location: India

Hi Murthy,

You can code STEP1 to give two return codes for the file values 1 and 0.

Based on the return code of STEP1, STEP2 Steplib can be changed.

// IF STEP1.RC EQ 0 THEN
//STEP2A EXEC PGM=P1
//STEPLIB DD DSN=LOAD1 LIBRARY
.
.
// ELSE
//STEP2B EXEC PGM=P1
//STEPLIB DD DSN=LOAD2 LIBRARY
.
.
// ENDIF

Regards,
SJ

Anuj D. · Posted: Tue May 27, 2008 5:04 pm Post subject:

Hi,

Might be with a little trick this can be done, but in any case I would suggest to revise the logic to execute two different programs. .. ofcourse if You want to use two different load-libraries with same program name, they are nothing but two different load modules/programs..

gcicchet · Senior Member Joined: 28 Jul 2006 Posts: 438

Murthy,
as Dick has stated previously, you cannot achieve this without repeating the steps, you cannot include just the STEPLIB based on previous step return code.

You will need somthing like SJ has mentioned.

Here is a way of achieving this

dick scherrer · Posted: Tue May 27, 2008 11:02 pm Post subject:

Hello,

When i posted that you can't do what you asked with jcl, i (foolishly) figured that you would find a more proper implementation.

This may sound a bit strong, but it is a very bad practice to have the same production program name in different loadlibs - it should not be allowed. If the functionality is actually different, there should be 2 names. If there is only a slight difference, a single module with a PARM might be a good choice.

Sounds like there is no configuration management in place or this would not even be a question. Does this mean that the source code is also not managed?

Anuj D. · Posted: Wed May 28, 2008 10:50 am Post subject:

Hi,

Lets' leave all the discussion, please let me know why there are two different libreairs for a single load-module; I might sound dumb, but I've never used this type of approach & then why should I use, what's the benefit.

dick scherrer · Posted: Wed May 28, 2008 8:53 pm Post subject:

Hi Anuj,

It is good that you have not

- it is yet another thing that can be done but should not be done.

There is no real benefit. It is done because a proper way is not used (due to not knowing any better or someone wanting some short-cut).

Anuj D. · Posted: Thu May 29, 2008 11:18 am Post subject:

expat · Posted: Thu May 29, 2008 12:02 pm Post subject:

You can also use IDCAMS.
Note the use of PARM= on the EXEC card to ensure that the value will not be ignored if it is in CC01.

You can then use normal IF/THEN/ELSE to check the RC from the previous step

birdy K · New User Joined: 05 Mar 2008 Posts: 43 Location: chennai

Hi everyone,

I have a doubt that we can concatenate a libraries for a single program. If it not found there in first library , it will search in second library. Isnt it? If there is any change in pgm, the load module will be different. So I think the load module will not be different . Only load libraries name will be different. If I am wrong, Please guide me.

Anuj D. · Posted: Thu May 29, 2008 1:12 pm Post subject:

dick scherrer · Posted: Thu May 29, 2008 7:17 pm Post subject:

Hello,

stodolas · Posted: Thu May 29, 2008 7:23 pm Post subject:

We have 8 loadlibs for our programs.

PROD.BATCH.LOADLIB
PROD.CICS.LOADLIB
BENCH.BATCH.LOADLIB
BENCH.CICS.LOADLIB
CLIENT.BATCH.LOADLIB
CLIENT.CICS.LOADLIB
UNIT.BATCH.LOADLIB
UNIT.CICS.LOADLIB

A program can reside in all 4 (batch or CICS) at any given time. However we concatenate our loadlibs as follows:

Production batch/cics only looks to PROD.*.LOADLIB
Benchmark looks to BENCH.*.LOADLIB and PROD.*.LOADLIB
Client looks to CLIENT.*.LOADLIB and PROD.*.LOADLIB
Unit looks to UNIT.*.LOADLIB and PROD.*.LOADLIB

This ensures that even if a program isn't at the current promotion level it can look to prod to find what should be a working copy.

Anuj D. · Posted: Fri May 30, 2008 10:26 am Post subject:

Hi,