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. <r.skoru...@bremultibank.com.pl> wrote:

> 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.
>
> BTW: some old RACF BE87 course manuals say the profiles in TSOPROC have
> to be discrete. It's not true.
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
>
>
>
> W dniu 23.03.2020 o 15:22, Robert Longabaugh pisze:
> > 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. <r.skoru...@bremultibank.com.pl>
> wrote:
> >
> >> 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 of (many possible)
> options.
> >> However TSOPROC is from TSO world. Indeed, user can overtype default
> value.
> >> However admin can restrict use any other procedure except the only one
> >> (two, three...) allowed.
> >>   From the other hand well configured and protected environment should
> >> not need such restriction. The worst things which could happen are:
> >> a) JCL error during logon
> >> b) some unaccessible options on ISPF screen.
> >>
> >> --
> >> Radoslaw Skorupka
> >> Lodz, Poland
> >>
> >>
> >>
> >>
>
>
>
> ======================================================================
>
> Jeśli nie jesteś adresatem tej wiadomości:
>
> - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
> - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
> zapisałeś na dysku).
> Wiadomość ta może zawierać chronione prawem informacje, które może
> wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia
> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania,
> narusza prawo i może podlegać karze.
>
> mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
> www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy
> XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, NIP:
> 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
> 01.01.2020 r. wynosi 169.401.468 złotych.
>
> If you are not the addressee of this message:
>
> - let us know by replying to this e-mail (thank you!),
> - delete this message permanently (including all the copies which you have
> printed out or saved).
> This message may contain legally protected information, which may be used
> exclusively by the addressee.Please be reminded that anyone who
> disseminates (copies, distributes) this message or takes any similar
> action, violates the law and may be penalised.
>
> mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
> Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the
> Capital City of Warsaw, 12th Commercial Division of the National Court
> Register, KRS 0000025237, NIP: 526-021-50-88. Fully paid-up share capital
> amounting to PLN 169.401.468 as at 1 January 2020.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to