Execution of Macro at Command Line on a Mainframe Logon

RahulG31 · Active User Joined: 20 Dec 2014 Posts: 446 Location: USA

Hi,

I am providing a rexx macro on the command line on a mainframe logon screen (See screenshot).
The problem is that when I login, i.e. when I go to ISPF from TSO, the rexx script remains unexecuted.
But when I try to logoff the session, i.e. go back to TSO from ISPF then the script actually runs.

I am not sure what do I need to do for my script to be executed at logon time and not at logoff.

The rexx is a simple setup step to add library to SYSEXEC.

Please help so that my script runs each time I login.

Thanks
Rahul

Pedro · Posted: Mon Dec 22, 2014 7:58 pm

I am sure the logon proc is already executing some setup execs, and that exec is starting ISPF. The exec you provide will be executed after the system logon exec, but the system exec does not finish until ISPF returns control.

You need to add your customization to the existing setup process.

RahulG31 · Active User Joined: 20 Dec 2014 Posts: 446 Location: USA

Thanks for the reply Pedro!

I was under impression that whatever rexx macro I give (at the command line) will run when I logon.

If it doesn't run when I login then what is the point in having a command line which is not able to run a macro.

Is it not working because it is a setup script ?

I'll really appreciate if you could clear my doubt.

Mickeydusaor · Posted: Mon Dec 22, 2014 8:18 pm

It depends on the two(2) TSO user exits and how they are setup. It appears that your Rexx is exec at sign off and not at sign on and this how someone in your shop has decided that they want your ISPF sessions to function.

RahulG31 · Active User Joined: 20 Dec 2014 Posts: 446 Location: USA

Thanks Mickeydusaor!

That's more likely to be the cause. Is there any work around available for this problem?

Mickeydusaor · Posted: Mon Dec 22, 2014 8:59 pm

talk to your Tech Support and have them change your TSO logon proc to the user exit that will execute your Rexx at sign on it they have one setup.

James Halley · New User Joined: 11 Apr 2012 Posts: 18 Location: USA

The article at the following web address explains a popular method of accomplishing what you want:

steve-myers · Posted: Mon Dec 22, 2014 9:57 pm

As Pedro noted, many installations execute a startup script when you logon. This has nothing to do with the command you specify in the logon panel. The command in your logon panel executes after the installation logon script. The installation logon script is specified in the logon proc.

RahulG31 · Active User Joined: 20 Dec 2014 Posts: 446 Location: USA

Thanks All for your responses. As you all have mentioned, the best thing would be to talk to Tech support. Let's see what they say.

Thanks again for your time.

Pedro · Posted: Tue Dec 23, 2014 3:00 am

I think the situation is that you have two methods to customize your logon: 1) executed by logon proc and
2) specified in logon panel.

The system tries to run both, serially. The only problem is that the first method involves a long process (ISPF) and so the second method does not run on a timely basis.

You have two choices to resolve:
1) move your customization to the logon proc executed exec. or,
2) move the ISPF start from the logon proc executed exec to your logon panel specified exec. This will cause the second exec to execute before you start ISPF.