Vince Coen wrote:
>Anyone have the JCL to set up a new user for TSO and other services for both
>OS/390 and Z/OS.
Sri h Kolusu gave you excellent TSO screen samples in a webpage. David Gibney
gave you a good warning.
What services? Ok, that webpage gave you some details for SDSF.
Ok, for JCL, try this fun one for new id with name PEST (loosely based on that
webpage).
//STEP1 EXEC PGM=IKJEFT01
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
PROFILE NOPREFIX
adduser PEST special operations password(password) +
name('BREAKER ') +
owner(SYS1) +
tso( acctnum(ACCT#) +
proc(ISPFPROC) +
size(1280000) +
unit(SYSDA) +
) +
dfltgrp(SYS1)
permit ISPFPROC cl(TSOPROC ) ac(READ) id(PEST ) <-- if you don't use
UACC=READ for SYS1 connection.
Look at that webpage for more permits.
You may need to review RACF classes like SDSF, TSOPROC, TSOAUTH, SDSF,
JESSPOOL, OPERCMDS, etc.
Also review access to Mcat, Ucats and the HLQ used in logons as well your TSO
id own HLQ (access to Own HLQ datasets is not really a concern since generally
you will get ALTER access anyways by default.)
Oh, if you're having trouble using SDSF, type in WHO in SDSF and review your
TSOAUTH access according to what you see.
>Getting bored using IBMUSER and when trying to use TSO commands to do it have
>made a bit of a mess as it does not seem to work correctly (this could be me!)
>and no I do not wish to use the other default names but a specific one or two?
What mess? Please post error messages and attempts. There are no other defaults
AFAIK.
>This is assuming that the procedure is the same for both :)
No. sysctlg and vsamdset are properly dead in z/OS the last time I checked. You
may need to review access to OMVS in z/OS.
Good luck and just test repeatedly out the new id before revoking IBMUSER.
Groete / Greetings
Elardus Engelbrecht
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
