MVSFORUMS.com

Bithead

I am trying to get a storage report for a DB2 job that runs under IKJEFT01. I am able to get it by using the option "PARMS=(/RPTSTG)" within the DSN statement but I would really like to define it on the EXEC statement as "EXEC IKJEFT01,PARM='/RPTSTG'". When I do this, I get an error. Does anyone know how to pass run-time options directly to IKJEFT01?

kolusu · Posted: Wed Nov 16, 2005 12:27 pm Post subject:

Bithead,

As far as I Know , if it is DB2 process, you cannot directly pass parms to IKJEFT01 on a exec statement.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

Bithead · Posted: Wed Nov 16, 2005 2:53 pm Post subject:

I am trying to apply the option to a number of processes and I was hoping I could change the procedure. Thanks Kolusu.

semigeezer · Posted: Wed Nov 16, 2005 4:41 pm Post subject:

Wen you start TSO (IKJEFT01), you can pass parameters on the PARM statement. The parameter is the name of the initial command you want to execute. So you should be able to create a Rexx exec that just takes a parameter and runs the commands you want to run. So something like this...

Bithead · Posted: Wed Nov 16, 2005 4:45 pm Post subject:

Semigeezer - it doesn't seem to work with DB2, probably because the PARM is considered as another source for SYSIN. When I try it, I get "IKJ56621I INVALID COMMAND NAME SYNTAX".

semigeezer · Posted: Wed Nov 16, 2005 4:47 pm Post subject:

Can you show what you've done?

Bithead · Posted: Wed Nov 16, 2005 4:52 pm Post subject:

semigeezer · Posted: Wed Nov 16, 2005 5:13 pm Post subject:

You are trying to execue the command /RPTSTG which is not valid TSO command name syntax.

I've never used the DSN command though I know it has some odd behaviours. I don't know how you'd pass it bsically 2 parameters. Maybe some form of TSO's CALL command (within a called CLIST or exec). How does this get invoked not using TSO?

Bithead · Posted: Thu Nov 17, 2005 8:57 am Post subject:

I am trying to get Language Environment Storage Reports for DB2 jobs without modifying the jobs themselves. I can run the jobs in test but the resources are not allocated the same as production. I would like to modify the global parameters and I am trying to run a baseline.

semigeezer · Posted: Thu Nov 17, 2005 10:04 am Post subject:

I understand what you are trying to do, but what does a sample job that pases the LE parms look like? If I understand how it looks in JCL, I might be able to give you a similar method for use in TSO.

Bithead · Posted: Thu Nov 17, 2005 10:09 am Post subject:

Here is my COBOL sample JCL using "Hello World":

semigeezer · Posted: Thu Nov 17, 2005 1:45 pm Post subject:

I can't try to help without sufficient information. I know how to pass parameters to a program in JCL. How does this work with the DSN command? There must be a program you are invoking, and are there then inline control statements? What does a job that invokes DSN statements look like?

You need to simulate exactly what is being done in JCL from within the TSO TMP. That can be done in several ways (TSO CALL command, ISPF's SELECT PGM() PARM() commands, SELECT CMD() followed by SELECT PGM() if using ISPLLIB, assembler calls to IKJTSR, etc) but without knowing how the DSN command is really invoked from JCL, I can't suggest a method of invocation that will be the same as in JCL but from within TSO instead.

Without knowing the exact environment, I'd suggest
Add all necessary program libraries to STEPLIB (not ISPLLIB) and invoke ISPF in batch, then call a CLIST that uses ISPEXEC SELECT PGM(...) PARM(/RPTOPTS(ON)) to call the program that processes the DSN command. I say this because ISPEXEC SELECT PGM() sets up register 1 to point to the same type of parameter list that JCL's PARM= clause creates. The problem with the DSN command (and I don't even know what DSN does) is that it uses dynamic calls that must be in STEPLIB to work under ISPF. If you get S806 abends, then that is probably the problem.

I can't gaurentee that this will work, but it is my best guess.

Bithead · Posted: Thu Nov 17, 2005 2:23 pm Post subject:

I found a reference on passing run-time parameters to application running under batch TSO and it involves use of the CALL statement which defeats the object. If I need to change the format of the program invocation, I may as well code the PARMS() statement.

I don't think I will be able to do what I wanted so I will have to fall back on running applications out of test.

semigeezer, thanks for your help but I don't think that I can persue this any further. Sad