works fine for the much neglected REXX/CICS too.

REXX/CICS also has online help:

14.3.50  USERID

_______________



+----------------------------------------------------------------------------+
|
  |
|
>>--USERID()------------------------------------------------------------>< |
|
  |
+----------------------------------------------------------------------------+


returns the CICS signon user ID if the user is signed onto CICS or the
CICS
region default user ID (if one was specified by the CICS systems
programmer).
User IDs are padded on the right with blanks so that the returned value is

always eight bytes long.



Here is an example:



USERID()    ->    'ARTHUR' /* Maybe */



When I gave a presentation at Share in 2019, some people thought it was
*NEW*.


On Thu, Feb 17, 2022 at 10:38 AM Charles Mills <[email protected]> wrote:

> If you are subject to PCI DSS then you have PCI DSS audits (and no, I am
> not an expert on the details).
>
> Like any other audit standard -- maybe they catch you and maybe they don't.
>
> My *perception* is that the standard is aimed at a situation you may have
> seen: a retail store or similar that has some sort of management software
> and for reasons of laziness, ignorance or limited licensed seats every
> clerk is using the same login.
>
> RACF userids don't cost anything -- why would you not create one (or more)
> for each user? I suppose there are ISV products that are licensed by the
> named seat.
>
> Charles
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Pommier, Rex
> Sent: Wednesday, February 16, 2022 2:41 PM
> To: [email protected]
> Subject: Re: [EXTERNAL] Re: How to Get UserID in non-TSO REXX
>
> It probably is but PCI DSS is a standard.  How does one electronically
> enforce it?  My security team can have everybody sign a statement saying
> they won't share their ID/password with their buddy at the next desk but
> that won't physically stop them.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>


-- 
Wayne V. Bickerdike

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to