IBM Mainframe Forum

Hi,

I have jobs calling a custom command implemented in TSO/E:


Looking at the documentation, this 'SAU002' keyword refers to a specific command added to TSO/E.

How can I see and possibly change its definition?

RalphEagle wrote:Hi,

I have jobs calling a custom command implemented in TSO/E:

Select all

//STEP005  EXEC PGM=IKJEFT1A,DYNAMNBR=20,
//         PARM='SAU002'

Looking at the documentation, this 'SAU002' keyword refers to a specific command added to TSO/E.

How can I see and possibly change its definition?

As long as you don’t know where the TSO commands can be located, or at least - what the “TSO commands are”, - I recommend you not to start thinking about “changing its definition”

This SAU002 is likely a home-made program added to your company environment by your system administrator. Ask your Helpdesk for any advice.

These users thanked the author sergeyken for the post:

RalphEagle (Wed Jul 21, 2021 7:14 pm)

Knowing where TSO commands are located is what I implied with 'How can I see' part of the question. So there is no convention about this, only way to go is ask where they are located because this is dependent on the company environment?

RalphEagle wrote:Knowing where TSO commands are located is what I implied with 'How can I see' part of the question. So there is no convention about this, only way to go is ask where they are located because this is dependent on the company environment?

These are all the basics…

First of all you need to confirm with your Helpdesk or administration that this SAU002 is really a specific home-made command for your company. (It can be also created differently: a compiled load module, a script in CLIST/REXX, etc.).

Depending on those facts, the “command” itself may be stored in various locations - from SYS1.LINKLIB to any other library, either system-wide one defined in your local LINKLIST, or in one of local libraries defined in specific JCL/procedures as //JOBLIB, //STEPLIB (for load modules), or in //SYSEXEC, //SYSPROC (for CLIST/REXX scripts).

Those theoretical advices can be continued endlessly (when starting from zero level knowledge). You need yourself:
1) inquire at your company about the origins of this “command”
2) inquire what is the type of this “command” - module? script? something else?
3) get confirmed that you have no rights to touch this “command” in any manner

I asked the system admins who told me this a Rexx procedure stored in a specific library. I could go and have a look; thank you!!

The poster did not provide the complete JCL. In the simplest case, the rexx program will be in either the concatenation for the SYSEXEC DD or in the SYSPROC DD.

Also, the concatenations in JCL frequently match those used in TSO. Learn to use the TSO ISRDDN command with it's MEMBER subcommand. It will show you where the member is.

These users thanked the author Pedro for the post:

RalphEagle (Fri Jul 30, 2021 12:56 pm)

Yes the library was in fact in an include member containing a lot of DD, one of those being that library.

I tried the TSO ISRDDN command with the MEMBER subcommand and could find the member in the library mentioned by the admin. That was an option I was actually looking for; thank you!!

RalphEagle wrote:Yes the library was in fact in an include member containing a lot of DD, one of those being that library.

I tried the TSO ISRDDN command with the MEMBER subcommand and could find the member in the library mentioned by the admin. That was an option I was actually looking for; thank you!!

Your original question

How can I see and possibly change its definition?

has nothing to do with what you really needed…

has nothing to do with what you really needed

I disagree. With ISRDDN and MEMBER command, you are shown the concatenation (see/find it) and I think you can issue B or E line commands to browse or edit (to possibly change it).