IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Alter User LOGON Script Parameters


IBM Mainframe Forums -> CLIST & REXX
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Ron Barnes

New User


Joined: 09 Mar 2021
Posts: 5
Location: USA

PostPosted: Wed Mar 10, 2021 12:04 am
Reply with quote

Hello All,

This is my first post so please bear with me as I become accustomed to this forum.

I am NOT a z/OS Admin. I am a COBOL Programmer that knows his way around a mainframe.
That being said.
I have been assigned to a new group in my organization. I am there to just support my groups access to the mainframe. IE... Assign user names, reset passwords, connect DB2 Databases to users. Pretty much the mundane stuff that a real admin does not have the time to do.

I was asked to alter the Logon Scrips for all users in order to update the IMS320 Datasets to use IMS322. I can work my way around REXX and JCL. The issue I'm having is I cannot find where the Logon scrips would be kept nor what they would be called. When I made a passing query to a co-worker, the response was 'it's in with the JCL'.

I found a few *.*.JCL PDS's in the mainframe and looking through them, I do not seem to be able to locate what I'm trying to change.

Would anyone here have any insights (Generically of course) as to what a logon script would be called and where it may be found?

Regards,

-Ron
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 884
Location: The Universe

PostPosted: Wed Mar 10, 2021 12:12 am
Reply with quote

The default LOGON proc has //SYSEXEC an/or //SYSPROC DD statements. Start there.

The usual LOGON script is started by

// EXEC PGM=IKJEFT01,PARM='TSO command to start the LOGON script'

in the LOGON proc.
Back to top
View user's profile Send private message
Ron Barnes

New User


Joined: 09 Mar 2021
Posts: 5
Location: USA

PostPosted: Wed Mar 10, 2021 12:22 am
Reply with quote

steve-myers wrote:
The default LOGON proc has //SYSEXEC an/or //SYSPROC DD statements. Start there.

The usual LOGON script is started by

// EXEC PGM=IKJEFT01,PARM='TSO command to start the LOGON script'

in the LOGON proc.


Thank you!
Back to top
View user's profile Send private message
daveporcelan

Active Member


Joined: 01 Dec 2006
Posts: 756
Location: Pennsylvania

PostPosted: Wed Mar 10, 2021 12:32 am
Reply with quote

To see your logon proc and input parms,and find script.

In SDSF:
DA OTSU - See all active users
Select your user ID to see your logon proc
Find your logon script as shown by Steve above - PARM=

Another way to find this script:
TSO ISRDDN - From any command line shows datasets allocated to your tso session
Then:
MEM Scriptname - Will find the script within your allocation
Under ACT use V to view this script
Back to top
View user's profile Send private message
Ron Barnes

New User


Joined: 09 Mar 2021
Posts: 5
Location: USA

PostPosted: Wed Mar 10, 2021 1:44 am
Reply with quote

daveporcelan wrote:
To see your logon proc and input parms,and find script.

In SDSF:
DA OTSU - See all active users
Select your user ID to see your logon proc
Find your logon script as shown by Steve above - PARM=

Another way to find this script:
TSO ISRDDN - From any command line shows datasets allocated to your tso session
Then:
MEM Scriptname - Will find the script within your allocation
Under ACT use V to view this script


This got me exactly where I wanted to be!!

Thank you Sir!

Thank you Both!
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2227
Location: Silicon Valley

PostPosted: Wed Mar 10, 2021 11:17 am
Reply with quote

Additional info:
Look in SYS1.PROCLIB(JES2) for the PROC00 DD name. That will show you the names of the PDSes that have the logon procs.
Back to top
View user's profile Send private message
Joerg.Findeisen

Active User


Joined: 15 Aug 2015
Posts: 475
Location: Bamberg, Germany

PostPosted: Wed Mar 10, 2021 11:31 am
Reply with quote

Pedro wrote:
Additional info:
Look in SYS1.PROCLIB(JES2) for the PROC00 DD name. That will show you the names of the PDSes that have the logon procs.

Use $d proclib instead.
Code:
$HASP319 PROCLIB(PROC00)                                     
$HASP319 PROCLIB(PROC00)    DD(1)=(DSNAME=<dsn>), ..
Back to top
View user's profile Send private message
Willy Jensen

Active User


Joined: 01 Sep 2015
Posts: 450
Location: Denmark

PostPosted: Wed Mar 10, 2021 2:33 pm
Reply with quote

also:
TSO LU your-userid TSO NORACF
to check if an initial command has been defined.
Back to top
View user's profile Send private message
Ron Barnes

New User


Joined: 09 Mar 2021
Posts: 5
Location: USA

PostPosted: Wed Mar 10, 2021 5:15 pm
Reply with quote

This Place is Awesome!!
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Wed Mar 10, 2021 6:53 pm
Reply with quote

Just a thought that may make things easier in the future ...

One of the things that I used to do back in the day when I was responsible for the SAS installations and maintenance, was the use of aliases, which meant that we could upgrade software without changes to the user procs or jobs that they submitted.

basically
SASPROD was aliased to SAS93 .... the 9.3 version
SASTEST was aliased to SAS94

So when the testing was complete and everyone happy, all we had to do was to redefine the alias to point to the new version of the software

Of course sometimes we had to add or remove a DD statement, but using PROCs made the changes minimal, and once again in one centralised library.
Back to top
View user's profile Send private message
Ron Barnes

New User


Joined: 09 Mar 2021
Posts: 5
Location: USA

PostPosted: Wed Mar 10, 2021 7:03 pm
Reply with quote

expat wrote:
Just a thought that may make things easier in the future ...

One of the things that I used to do back in the day when I was responsible for the SAS installations and maintenance, was the use of aliases, which meant that we could upgrade software without changes to the user procs or jobs that they submitted.

basically
SASPROD was aliased to SAS93 .... the 9.3 version
SASTEST was aliased to SAS94

So when the testing was complete and everyone happy, all we had to do was to redefine the alias to point to the new version of the software

Of course sometimes we had to add or remove a DD statement, but using PROCs made the changes minimal, and once again in one centralised library.


That is a very good idea. Kind of like using Symbolic in JCL?

Regards,
-Ron
Back to top
View user's profile Send private message
Willy Jensen

Active User


Joined: 01 Sep 2015
Posts: 450
Location: Denmark

PostPosted: Wed Mar 10, 2021 10:17 pm
Reply with quote

Re alias, I will suggest that you also look at SYMRELATE, i.e.
DEF ALIAS(NAME(SYSA.PROCLIB) -
SYMBOLICRELATE(SYSA.&ZOSVER..PROCLIB))
Slightly more complex as you need to define a system symbol, in this sample ZOSVER, but afterwards you only have to change the symbol to affect multiple datasets. System symbols can be changed dynamically.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CLIST & REXX

 


Similar Topics
Topic Forum Replies
No new posts Embeding DB2 sql statements in scirpt... DB2 7
No new posts OMVS Shell Script not working properly. All Other Mainframe Topics 1
No new posts Trim values of parameters in JCL JCL & VSAM 2
No new posts Revoke on DB2 to remove an user DB2 4
This topic is locked: you cannot edit posts or make replies. Is there a way to restrict user login... All Other Mainframe Topics 11
Search our Forums:

Back to Top