No it is not tied to UADS. In the 1980s, I worked at a place that had
over 40 logon procs in one general applications data center. We reduced
that with dynamic allocation post-logon.
On Mon, Mar 23, 2020 at 7:32 AM R.S. wrote:
> Alternate logon proc? Is is something related to UADS?
>
Alternate logon proc? Is is something related to UADS?
Nowadays (that means: last 20 years) you can have as many logon procs as
you want (and allowed to).
The only thing is to overtype logon proc field on TSO logon screen. Of
course you need READ access to the profile covering the procedure.
If you are referring to an alternate logon proc so that you can have a
backout when you have changed the main logon proc or are doing other
maintenance, the syntax would be:
LOGON yourid PROC(procname)
Bob Longabaugh
Broadcom
Storage Management Products
On Fri, Mar 20, 2020 at 8:27 AM R.S.
W dniu 20.03.2020 o 15:35, Jake Anderson pisze:
Hello
Apologies for the dummy question
Is it possible to enforce logon proc name while we so LOGON APPLID(USERID) ?
As am unable to get into TSO login screen where I can modify the TSOPROC
value
When typing LOGON APPLID you choose TSO as one
Use RACF to protect the TSOPROC general resource profile.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Jake Anderson
Sent: Friday, March 20, 2020 10:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Forcing Logonproc USSMSG10
[External Email. Exercise caution when
