User record formats
The records associated with users are:
- User Basic Data
- User Categories
- User Classes
- User Group Connections
- User Installation Data
- User Connect Data
- User RRSF Data
- User Certificate Name
- User Mappings
- User Associated Distributed Mappings
- User DFP Data
- User TSO Data
- User CICS® Data
- User CICS Operator Classes
- User CICS RSL Keys
- User CICS TSL Keys
- User Language Data
- User OPERPARM Data
- User OPERPARM Scope
- User WORKATTR Data
- User OMVS Data
- User NETVIEW Segment
- User OPCLASS
- User DOMAINS
- User DCE Data
- User OVM Data
- User LNOTES Data
- User NDS Data
- User KERB Data
- User PROXY Data
- User EIM Data
- User CSDATA Custom Fields
User MFA Data
User basic data record (0200)
The User Basic Data record defines the basic information about a user. There is one record per user.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USBD_RECORD_TYPE | Int | 1 | 4 | Record type of the User Basic Data record (0200). |
| USBD_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USBD_CREATE_DATE | Date | 15 | 24 | The date that the profile was created. |
| USBD_OWNER_ID | Char | 26 | 33 | The user ID or group name that owns the profile. |
| USBD_ADSP | Char | 35 | 38 | Does the user have the ADSP attribute? Valid Values include "Yes" and "No". |
| USBD_SPECIAL | Char | 40 | 43 | Does the user have the SPECIAL attribute? Valid Values include "Yes" and "No". |
| USBD_OPER | Char | 45 | 48 | Does the user have the OPERATIONS attribute? Valid Values include "Yes" and "No". |
| USBD_REVOKE | Char | 50 | 53 | Is the user REVOKEd? Valid Values include "Yes" and "No". |
| USBD_GRPACC | Char | 55 | 58 | Does the user have the GRPACC attribute? Valid Values include "Yes" and "No". |
| USBD_PWD_INTERVAL | Int | 60 | 62 | The number of days that the user's password can be used. |
| USBD_PWD_DATE | Date | 64 | 73 | The date that the password was last changed. |
| USBD_PROGRAMMER | Char | 75 | 94 | The name associated with the user ID. |
| USBD_DEFGRP_ID | Char | 96 | 103 | The default group associated with the user. |
| USBD_LASTJOB_TIME | Time | 105 | 112 | The last recorded time that the user entered the system. |
| USBD_LASTJOB_DATE | Date | 114 | 123 | The last recorded date that the user entered the system. |
| USBD_INSTALL_DATA | Char | 125 | 379 | Installation-defined data. |
| USBD_UAUDIT | Char | 381 | 384 | Do all RACHECK and RACDEF SVCs cause logging? Valid Values include "Yes" and "No". |
| USBD_AUDITOR | Char | 386 | 389 | Does this user have the AUDITOR attribute? Valid Values include "Yes" and "No". |
| USBD_NOPWD | Char | 391 | 394 | "YES" indicates that this user ID can log on without
a password using OID card. "NO" indicates that this user must specify
a password. "PRO" indicates a protected user ID. "PHR" indicates that
the user has a password phrase. See also z/OS Security Server RACF Security Administrator's Guide. Note:
USBD_PWD_ALG and USBD_PHR_ALG are the suggested fields
to query to determine what combination of password and password phrase
exists for a user. |
| USBD_OIDCARD | Char | 396 | 399 | Does this user have OIDCARD data? Valid Values include "Yes" and "No". |
| USBD_PWD_GEN | Int | 401 | 403 | The current password generation number. |
| USBD_REVOKE_CNT | Int | 405 | 407 | The number of unsuccessful logon attempts. |
| USBD_MODEL | Char | 409 | 452 | The data set model profile name. |
| USBD_SECLEVEL | Int | 454 | 456 | The user's security level. |
| USBD_REVOKE_DATE | Date | 458 | 467 | The date that the user is revoked. |
| USBD_RESUME_DATE | Date | 469 | 478 | The date that the user is resumed. |
| USBD_ACCESS_SUN | Char | 480 | 483 | Can the user access the system on Sunday? Valid Values include "Yes" and "No". |
| USBD_ACCESS_MON | Char | 485 | 488 | Can the user access the system on Monday? Valid Values include "Yes" and "No". |
| USBD_ACCESS_TUE | Char | 490 | 493 | Can the user access the system on Tuesday? Valid Values include "Yes" and "No". |
| USBD_ACCESS_WED | Char | 495 | 498 | Can the user access the system on Wednesday? Valid Values include "Yes" and "No". |
| USBD_ACCESS_THU | Char | 500 | 503 | Can the user access the system on Thursday? Valid Values include "Yes" and "No". |
| USBD_ACCESS_FRI | Char | 505 | 508 | Can the user access the system on Friday? Valid Values include "Yes" and "No". |
| USBD_ACCESS_SAT | Char | 510 | 513 | Can the user access the system on Saturday? Valid Values include "Yes" and "No". |
| USBD_START_TIME | Time | 515 | 522 | After what time can the user log on? |
| USBD_END_TIME | Time | 524 | 531 | After what time can the user not log on? |
| USBD_SECLABEL | Char | 533 | 540 | The user's default security label. |
| USBD_ATTRIBS | Char | 542 | 549 | Other user attributes (RSTD for users with RESTRICTED attribute). |
| USBD_PWDENV_EXISTS | Char | 551 | 554 | Has a PKCS#7 envelope been created for the user's current password? Valid Values include "Yes" and "No". |
| USBD_PWD_ASIS | Char | 556 | 559 | Should the password be evaluated in the case entered? Valid Values include "Yes" and "No". |
| USBD_PHR_DATE | Date | 561 | 570 | The date the password phrase was last changed. |
| USBD_PHR_GEN | Int | 572 | 574 | The current password phrase generation number. |
| USBD_CERT_SEQN | Int | 576 | 585 | Sequence number that is incremented whenever a certificate for the user is added, deleted, or altered. The starting value might not be 0. |
| USBD_PPHENV_EXISTS | Char | 587 | 590 | Has the user's current password phrase been PKCS#7 enveloped for possible retrieval? Valid Values include "Yes" and "No". |
| USBD_PWD_ALG |
Char |
592 |
603 |
Algorithm that is used to protect passwords.
Possible values are "LEGACY", "KDFAES", and "NOPASSWORD". |
| USBD_LEG_PWDHIST_CT |
Int |
605 |
607 |
Number of legacy password history entries. |
| USBD_XPW_PWDHIST_CT |
Int |
609 |
611 |
Number of KDFAES password history entries. |
| USBD_PHR_ALG |
Char |
613 |
624 |
Algorithm that is used to protect password phrases.
Possible values are "LEGACY", "KDFAES", and "NOPHRASE". |
| USBD_LEG_PHRHIST_CT |
Int |
626 |
628 |
Number of legacy password phrase history entries. |
| USBD_XPW_PHRHIST_CT |
Int |
630 |
632 |
Number of KDFAES password phrase history entries. |
| USBD_ROAUDIT |
Char |
634 |
637 |
This user can have a ROAUDIT attribute. Valid
Values include "Yes" and "No". |
| USBD_MFA_FALLBACK |
Char |
639 |
641 |
This user can use a password or password phrase
to logon to the system when IBM® MFA is
unavailable. Valid Values include "Yes" and "No". |
User categories record (0201)
The User Categories record defines the categories to which the user has access. There is one record per user/category combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCAT_RECORD_TYPE | Int | 1 | 4 | Record type of the User Categories record (0201). |
| USCAT_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USCAT_CATEGORY | Int | 15 | 19 | Category to which the user has access. |
User classes record (0202)
The User Classes record defines the classes in which the user can create profiles. There is one record per user/class combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCLA_RECORD_TYPE | Int | 1 | 4 | Record type of the User Classes record (0202). |
| USCLA_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USCLA_CLASS | Char | 15 | 22 | A class in which the user is allowed to define profiles. |
User group connections record (0203)
The User Group Connections record defines the groups with which the user is associated. There is one record per user connection.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USGCON_RECORD_TYPE | Int | 1 | 4 | Record type of the User Group Connections record (0203). |
| USGCON_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USGCON_GRP_ID | Char | 15 | 22 | The group with which the user is associated. |
User installation data record (0204)
The User Installation Data record defines the user data associated with a user ID.
This record type contains the data stored in the USRCNT repeat group, which is a field in the RACF® database that is reserved for your installation's use. None of the RACF commands manipulate this field. Do not confuse this field with the USER_INSTALL_DATA field, shown in Table 1, which you enter into the database using the ADDUSER and ALTUSER commands.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USINSTD_RECORD_TYPE | Int | 1 | 4 | Record type of the User Installation Data record (0204). |
| USINSTD_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USINSTD_USR_NAME | Char | 15 | 22 | The name of the installation-defined field. |
| USINSTD_USR_DATA | Char | 24 | 278 | The data for the installation-defined field. |
| USINSTD_USR_FLAG | Char | 280 | 287 | The flag for the installation-defined field in the form X<cc>. |
User connect data record (0205)
The User Connect Data record defines the relationships between users and groups. There is one record per user connection.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCON_RECORD_TYPE | Int | 1 | 4 | Record type of the User Connect Data record (0205). |
| USCON_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USCON_GRP_ID | Char | 15 | 22 | The group name. |
| USCON_CONNECT_DATE | Date | 24 | 33 | The date that the user was connected. |
| USCON_OWNER_ID | Char | 35 | 42 | The owner of the user-group connection. |
| USCON_LASTCON_TIME | Time | 44 | 51 | Time that the user last connected to this group. |
| USCON_LASTCON_DATE | Date | 53 | 62 | Date that the user last connected to this group. |
| USCON_UACC | Char | 64 | 71 | The default universal access authority for all new resources the user defines while connected to the specified group. Valid values are NONE, READ, UPDATE, CONTROL, and ALTER. |
| USCON_INIT_CNT | Int | 73 | 77 | The number of RACINITs issued for this user/group combination. |
| USCON_GRP_ADSP | Char | 79 | 82 | Does this user have the ADSP attribute in this group? Valid Values include "Yes" and "No". |
| USCON_GRP_SPECIAL | Char | 84 | 87 | Does this user have GROUP-SPECIAL in this group? Valid Values include "Yes" and "No". |
| USCON_GRP_OPER | Char | 89 | 92 | Does this user have GROUP-OPERATIONS in this group? Valid Values include "Yes" and "No". |
| USCON_REVOKE | Char | 94 | 97 | Is this user revoked? Valid Values include "Yes" and "No". |
| USCON_GRP_ACC | Char | 99 | 102 | Does this user have the GRPACC attribute? Valid Values include "Yes" and "No". |
| USCON_NOTERMUACC | Char | 104 | 107 | Does this user have the NOTERMUACC attribute in this group? Valid Values include "Yes" and "No". |
| USCON_GRP_AUDIT | Char | 109 | 112 | Does this user have the GROUP-AUDITOR attribute in this group? Valid Values include "Yes" and "No". |
| USCON_REVOKE_DATE | Date | 114 | 123 | The date that the user's connection to the group is revoked. |
| USCON_RESUME_DATE | Date | 125 | 134 | The date that the user's connection to the group is resumed. |
User RRSF data record (0206)
The User RRSF data record defines the information required by RACF remote sharing facility (RRSF). There is one record per user/RRSF data combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USRSF_RECORD_TYPE | Int | 1 | 4 | Record type of the RRSF data record (0206). |
| USRSF_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USRSF_TARG_NODE | Char | 15 | 22 | Target node name. |
| USRSF_TARG_USER_ID | Char | 24 | 31 | Target user ID. |
| USRSF_VERSION | Int | 33 | 35 | Version of this record. |
| USRSF_PEER | Char | 37 | 40 | Is this a peer user ID? Valid Values include "Yes" and "No". |
| USRSF_MANAGING | Char | 42 | 45 | Is USRSF_NAME managing this ID? Valid Values include "Yes" and "No". |
| USRSF_MANAGED | Char | 47 | 50 | Is USRSF_NAME being managed by this ID? Valid Values include "Yes" and "No". |
| USRSF_REMOTE_PEND | Char | 52 | 55 | Is this remote RACF association pending? Valid Values include "Yes" and "No". |
| USRSF_LOCAL_PEND | Char | 57 | 60 | Is this local RACF association pending? Valid Values include "Yes" and "No". |
| USRSF_PWD_SYNC | Char | 62 | 65 | Is there password synchronization with this user ID? Valid Values include "Yes" and "No". |
| USRSF_REM_REFUSAL | Char | 67 | 70 | Was a system error encountered on the remote system? Valid Values include "Yes" and "No". |
| USRSF_DEFINE_DATE | Date | 72 | 81 | GMT date stamp for when this record was defined. |
| USRSF_DEFINE_TIME | Time | 83 | 97 | GMT time stamp for when this record was defined. |
| USRSF_ACCEPT_DATE | Date | 99 | 108 | GMT date stamp when this association was approved or refused. Based on the REMOTE_REFUSAL bit setting. |
| USRSF_ACCEPT_TIME | Time | 110 | 124 | GMT time stamp when this association was approved or refused. Based on the REMOTE_REFUSAL bit setting. |
| USRSF_CREATOR_ID | Char | 126 | 133 | User ID who created this entry. |
User certificate name record (0207)
The User Certificate Name record defines the names of the certificate profiles in the DIGTCERT class that are associated with this user ID.
Note: RACF does not unload
all fields in profiles in the DIGTCERT class. The digital certificate
itself is not readable text and is the only field in the CERTDATA
segment. Therefore, RACF bypasses
the unloading of the CERTDATA segment of general resource profiles.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCERT_RECORD_TYPE | Int | 1 | 4 | Record type of the user certificate name record (0207). |
| USCERT_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USCERT_CERT_NAME | Char | 15 | 260 | Digital certificate name. |
| USCERT_CERTLABL | Char | 262 | 293 | Digital certificate label. |
User associated mappings record (0208)
The User Associated Mappings Record defines the certificate name filter in the DIGTNMAP class associated with this user ID.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USNMAP_RECORD_TYPE | Int | 1 | 4 | Record type of the User Associated Mappings record (0208). |
| USNMAP_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USNMAP_LABEL | Char | 15 | 46 | The label associated with this mapping. |
| USNMAP_MAP_NAME | Char | 48 | 293 | The name of the DIGTNMAP profile associated with this user. |
User associated distributed mappings record (0209)
The User Associated Distributed Mappings Record defines the IDIDMAP class profile name associated with this user ID.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USDMAP_RECORD_TYPE | Int | 1 | 4 | Record type of the User Associated Distributed Mappings record (0209). |
| USDMAP_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USDMAP_LABEL | Char | 15 | 46 | The label associated with this mapping. |
| USDMAP_MAP_NAME | Char | 48 | 293 | The name of the IDIDMAP profile associated with
this user. Note: This value is stored in the RACF database in UTF-8 format. If possible,
database unload changes this value to the EBCDIC format. If not possible,
hexadecimal values are produced.
|
User MFA factor data record (020A)
The User MFA factor data record defines the basic information about a the MFA factor data.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USMFA_RECORD_TYPE | Int | 1 | 4 | Record type of the user Multifactor authentication data record (020A). |
| USMFA_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USMFA_FACTOR_NAME | Char | 15 | 34 | Factor name. |
| USMFA_FACTOR_ACTIVE | Date | 36 | 54 | Factor active date. Will be blank if factor is not ACTIVE. |
User MFA policies record (020B)
The user MFA policies record (020B)
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USMPOL_RECORD_TYPE | Int | 1 | 4 | Record type of the user Multi-factor authentication policies record (020B) |
| USMPOL_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USMPOL_POLICY_NAME | Char | 15 | 34 | MFA Policy name. |
User DFP data record (0210)
The User DFP Data record defines the information required by the System Managed Storage facility of the Data Facility Product (DFP). The fields in these records define the characteristics of the data that are created by the user. There is one record per user/DFP data combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USDFP_RECORD_TYPE | Int | 1 | 4 | Record type of the User DFP data record (0210). |
| USDFP_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USDFP_DATAAPPL | Char | 15 | 22 | Default application name for the user. |
| USDFP_DATACLAS | Char | 24 | 31 | Default data class for the user. |
| USDFP_MGMTCLAS | Char | 33 | 40 | Default management class for the user. |
| USDFP_STORCLAS | Char | 42 | 49 | Default storage class for the user. |
User TSO data record (0220)
The user TSO data record defines the information required by TSO/E. There is one record per TSO user.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USTSO_RECORD_TYPE | Int | 1 | 4 | Record type of the User TSO Data record (0220). |
| USTSO_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USTSO_ACCOUNT | Char | 15 | 54 | The default account number. |
| USTSO_COMMAND | Char | 56 | 135 | The command issued at LOGON. |
| USTSO_DEST | Char | 137 | 144 | The default destination identifier. |
| USTSO_HOLD_CLASS | Char | 146 | 146 | The default hold class. |
| USTSO_JOB_CLASS | Char | 148 | 148 | The default job class. |
| USTSO_LOGON_PROC | Char | 150 | 157 | The default logon procedure. |
| USTSO_LOGON_SIZE | Int | 159 | 168 | The default logon region size. |
| USTSO_MSG_CLASS | Char | 170 | 170 | The default message class. |
| USTSO_LOGON_MAX | Int | 172 | 181 | The maximum logon region size. |
| USTSO_PERF_GROUP | Int | 183 | 192 | The performance group associated with the user. |
| USTSO_SYSOUT_CLASS | Char | 194 | 194 | The default sysout class. |
| USTSO_USER_DATA | Char | 196 | 203 | The TSO user data, in hexadecimal in the form X<cccc>. |
| USTSO_UNIT_NAME | Char | 205 | 212 | The default SYSDA device. |
| USTSO_SECLABEL | Char | 214 | 221 | The default logon security label. |
User CICS data record (0230)
The User CICS data record defines the data required by the Customer Information Control System (CICS). There is one record per user/CICS data combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCICS_RECORD_TYPE | Int | 1 | 4 | Record type of the User CICS Data record (0230). |
| USCICS_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USCICS_OPIDENT | Char | 15 | 17 | The CICS operator identifier. |
| USCICS_OPPRTY | Int | 19 | 23 | The CICS operator priority. |
| USCICS_NOFORCE | Char | 25 | 28 | Is the extended recovery facility (XRF) NOFORCE option in effect? Valid Values include "Yes" and "No". |
| USCICS_TIMEOUT | Char | 30 | 34 | The terminal time-out value. Expressed in hh:mm |
User CICS operator classes record (0231)
The user CICS operator classes record defines the classes associated with a CICS operator. There is one record per user/CICS operator class combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCOPC_RECORD_TYPE | Int | 1 | 4 | Record type of the User CICS Operator Class record (0231). |
| USCOPC_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USCOPC_OPCLASS | Char | 15 | 17 | The class associated with the CICS operator. |
User CICS RSL keys record (0232)
The user CICS RSL keys record defines the resource security level (RSL) keys associated with a CICS user. There is one record per combination of user and CICS RSL key.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCRSL_RECORD_TYPE | Int | 1 | 4 | Record type of the User CICS RSL keys record (0232). |
| USCRSL_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USCRSL_KEY | Int | 15 | 19 | RSL key number. |
User CICS TSL keys record (0233)
The User CICS TSL keys record defines the transaction security level (TSL) keys for a CICS user. There is one record per combination of user and CICS TSL key.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCTSL_RECORD_TYPE | Int | 1 | 4 | Record type of the User CICS TSL keys record (0233). |
| USCTSL_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USCTSL_KEY | Int | 15 | 19 | TSL key number. |
User language data record (0240)
The user language data record defines the primary and default languages for the user. There is one record per user/language combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USLAN_RECORD_TYPE | Int | 1 | 4 | Record type of the User Language Data record (0240). |
| USLAN_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USLAN_PRIMARY | Char | 15 | 17 | The primary language for the user. |
| USLAN_SECONDARY | Char | 19 | 21 | The secondary language for the user. |
User OPERPARM data record (0250)
The user OPERPARM data record defines the operator characteristics for the user. There is one record per user/OPERPARM data combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USOPR_RECORD_TYPE | Int | 1 | 4 | Record type of the User OPERPARM Data record (0250). |
| USOPR_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USOPR_STORAGE | Int | 15 | 19 | The number of megabytes of storage that can be used for message queuing. |
| USOPR_MASTERAUTH | Char | 21 | 24 | Does this user have MASTER console authority? Valid Values include "Yes" and "No". |
| USOPR_ALLAUTH | Char | 26 | 29 | Does this user have ALL console authority? Valid Values include "Yes" and "No". |
| USOPR_SYSAUTH | Char | 31 | 34 | Does this user have SYSAUTH console authority? Valid Values include "Yes" and "No". |
| USOPR_IOAUTH | Char | 36 | 39 | Does this user have I/O console authority? Valid Values include "Yes" and "No". |
| USOPR_CONSAUTH | Char | 41 | 44 | Does this user have CONS console authority? Valid Values include "Yes" and "No". |
| USOPR_INFOAUTH | Char | 46 | 49 | Does this user have INFO console authority? Valid Values include "Yes" and "No". |
| USOPR_TIMESTAMP | Char | 51 | 54 | Do console messages contain a timestamp? Valid Values include "Yes" and "No". |
| USOPR_SYSTEMID | Char | 56 | 59 | Do console messages contain a system ID? Valid Values include "Yes" and "No". |
| USOPR_JOBID | Char | 61 | 64 | Do console messages contain a job ID? Valid Values include "Yes" and "No". |
| USOPR_MSGID | Char | 66 | 69 | Do console messages contain a message ID? Valid Values include "Yes" and "No". |
| USOPR_X | Char | 71 | 74 | Are the job name and system name to be suppressed for messages issued from the JES3 global processor? Valid Values include "Yes" and "No". |
| USOPR_WTOR | Char | 76 | 79 | Does the console receive WTOR messages? Valid Values include "Yes" and "No". |
| USOPR_IMMEDIATE | Char | 81 | 84 | Does the console receive immediate messages? Valid Values include "Yes" and "No". |
| USOPR_CRITICAL | Char | 86 | 89 | Does the console receive critical event messages? Valid Values include "Yes" and "No". |
| USOPR_EVENTUAL | Char | 91 | 94 | Does the console receive eventual event messages? Valid Values include "Yes" and "No". |
| USOPR_INFO | Char | 96 | 99 | Does the console receive informational messages? Valid Values include "Yes" and "No". |
| USOPR_NOBRODCAST | Char | 101 | 104 | Are broadcast messages to this console suppressed? Valid Values include "Yes" and "No". |
| USOPR_ALL | Char | 106 | 109 | Does the console receive all messages? Valid Values include "Yes" and "No". |
| USOPR_JOBNAMES | Char | 111 | 114 | Are job names monitored? Valid Values include "Yes" and "No". |
| USOPR_JOBNAMEST | Char | 116 | 119 | Are job names monitored with timestamps displayed? Valid Values include "Yes" and "No". |
| USOPR_SESS | Char | 121 | 124 | Are user IDs displayed with each TSO initiation and termination? Valid Values include "Yes" and "No". |
| USOPR_SESST | Char | 126 | 129 | Are user IDs and timestamps displayed with each TSO initiation and termination? Valid Values include "Yes" and "No". |
| USOPR_STATUS | Char | 131 | 134 | Are data set names and dispositions displayed with each data set that is freed? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE001 | Char | 136 | 139 | Is this console enabled for route code 001? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE002 | Char | 141 | 144 | Is this console enabled for route code 002? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE003 | Char | 146 | 149 | Is this console enabled for route code 003? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE004 | Char | 151 | 154 | Is this console enabled for route code 004? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE005 | Char | 156 | 159 | Is this console enabled for route code 005? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE006 | Char | 161 | 164 | Is this console enabled for route code 006? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE007 | Char | 166 | 169 | Is this console enabled for route code 007? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE008 | Char | 171 | 174 | Is this console enabled for route code 008? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE009 | Char | 176 | 179 | Is this console enabled for route code 009? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE010 | Char | 181 | 184 | Is this console enabled for route code 010? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE011 | Char | 186 | 189 | Is this console enabled for route code 011? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE012 | Char | 191 | 194 | Is this console enabled for route code 012? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE013 | Char | 196 | 199 | Is this console enabled for route code 013? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE014 | Char | 201 | 204 | Is this console enabled for route code 014? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE015 | Char | 206 | 209 | Is this console enabled for route code 015? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE016 | Char | 211 | 214 | Is this console enabled for route code 016? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE017 | Char | 216 | 219 | Is this console enabled for route code 017? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE018 | Char | 221 | 224 | Is this console enabled for route code 018? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE019 | Char | 226 | 229 | Is this console enabled for route code 019? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE020 | Char | 231 | 234 | Is this console enabled for route code 020? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE021 | Char | 236 | 239 | Is this console enabled for route code 021? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE022 | Char | 241 | 244 | Is this console enabled for route code 022? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE023 | Char | 246 | 249 | Is this console enabled for route code 023? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE024 | Char | 251 | 254 | Is this console enabled for route code 024? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE025 | Char | 256 | 259 | Is this console enabled for route code 025? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE026 | Char | 261 | 264 | Is this console enabled for route code 026? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE027 | Char | 266 | 269 | Is this console enabled for route code 027? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE028 | Char | 271 | 274 | Is this console enabled for route code 028? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE029 | Char | 276 | 279 | Is this console enabled for route code 029? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE030 | Char | 281 | 284 | Is this console enabled for route code 030? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE031 | Char | 286 | 289 | Is this console enabled for route code 031? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE032 | Char | 291 | 294 | Is this console enabled for route code 032? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE033 | Char | 296 | 299 | Is this console enabled for route code 033? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE034 | Char | 301 | 304 | Is this console enabled for route code 034? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE035 | Char | 306 | 309 | Is this console enabled for route code 035? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE036 | Char | 311 | 314 | Is this console enabled for route code 036? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE037 | Char | 316 | 319 | Is this console enabled for route code 037? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE038 | Char | 321 | 324 | Is this console enabled for route code 038? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE039 | Char | 326 | 329 | Is this console enabled for route code 039? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE040 | Char | 331 | 334 | Is this console enabled for route code 040? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE041 | Char | 336 | 339 | Is this console enabled for route code 041? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE042 | Char | 341 | 344 | Is this console enabled for route code 042? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE043 | Char | 346 | 349 | Is this console enabled for route code 043? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE044 | Char | 351 | 354 | Is this console enabled for route code 044? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE045 | Char | 356 | 359 | Is this console enabled for route code 045? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE046 | Char | 361 | 364 | Is this console enabled for route code 046? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE047 | Char | 366 | 369 | Is this console enabled for route code 047? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE048 | Char | 371 | 374 | Is this console enabled for route code 048? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE049 | Char | 376 | 379 | Is this console enabled for route code 049? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE050 | Char | 381 | 384 | Is this console enabled for route code 050? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE051 | Char | 386 | 389 | Is this console enabled for route code 051? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE052 | Char | 391 | 394 | Is this console enabled for route code 052? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE053 | Char | 396 | 399 | Is this console enabled for route code 053? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE054 | Char | 401 | 404 | Is this console enabled for route code 054? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE055 | Char | 406 | 409 | Is this console enabled for route code 055? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE056 | Char | 411 | 414 | Is this console enabled for route code 056? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE057 | Char | 416 | 419 | Is this console enabled for route code 057? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE058 | Char | 421 | 424 | Is this console enabled for route code 058? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE059 | Char | 426 | 429 | Is this console enabled for route code 059? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE060 | Char | 431 | 434 | Is this console enabled for route code 060? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE061 | Char | 436 | 439 | Is this console enabled for route code 061? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE062 | Char | 441 | 444 | Is this console enabled for route code 062? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE063 | Char | 446 | 449 | Is this console enabled for route code 063? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE064 | Char | 451 | 454 | Is this console enabled for route code 064? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE065 | Char | 456 | 459 | Is this console enabled for route code 065? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE066 | Char | 461 | 464 | Is this console enabled for route code 066? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE067 | Char | 466 | 469 | Is this console enabled for route code 067? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE068 | Char | 471 | 474 | Is this console enabled for route code 068? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE069 | Char | 476 | 479 | Is this console enabled for route code 069? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE070 | Char | 481 | 484 | Is this console enabled for route code 070? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE071 | Char | 486 | 489 | Is this console enabled for route code 071? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE072 | Char | 491 | 494 | Is this console enabled for route code 072? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE073 | Char | 496 | 499 | Is this console enabled for route code 073? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE074 | Char | 501 | 504 | Is this console enabled for route code 074? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE075 | Char | 506 | 509 | Is this console enabled for route code 075? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE076 | Char | 511 | 514 | Is this console enabled for route code 076? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE077 | Char | 516 | 519 | Is this console enabled for route code 077? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE078 | Char | 521 | 524 | Is this console enabled for route code 078? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE079 | Char | 526 | 529 | Is this console enabled for route code 079? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE080 | Char | 531 | 534 | Is this console enabled for route code 080? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE081 | Char | 536 | 539 | Is this console enabled for route code 081? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE082 | Char | 541 | 544 | Is this console enabled for route code 082? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE083 | Char | 546 | 549 | Is this console enabled for route code 083? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE084 | Char | 551 | 554 | Is this console enabled for route code 084? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE085 | Char | 556 | 559 | Is this console enabled for route code 085? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE086 | Char | 561 | 564 | Is this console enabled for route code 086? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE087 | Char | 566 | 569 | Is this console enabled for route code 087? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE088 | Char | 571 | 574 | Is this console enabled for route code 088? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE089 | Char | 576 | 579 | Is this console enabled for route code 089? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE090 | Char | 581 | 584 | Is this console enabled for route code 090? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE091 | Char | 586 | 589 | Is this console enabled for route code 091? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE092 | Char | 591 | 594 | Is this console enabled for route code 092? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE093 | Char | 596 | 599 | Is this console enabled for route code 093? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE094 | Char | 601 | 604 | Is this console enabled for route code 094? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE095 | Char | 606 | 609 | Is this console enabled for route code 095? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE096 | Char | 611 | 614 | Is this console enabled for route code 096? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE097 | Char | 616 | 619 | Is this console enabled for route code 097? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE098 | Char | 621 | 624 | Is this console enabled for route code 098? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE099 | Char | 626 | 629 | Is this console enabled for route code 099? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE100 | Char | 631 | 634 | Is this console enabled for route code 100? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE101 | Char | 636 | 639 | Is this console enabled for route code 101? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE102 | Char | 641 | 644 | Is this console enabled for route code 102? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE103 | Char | 646 | 649 | Is this console enabled for route code 103? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE104 | Char | 651 | 654 | Is this console enabled for route code 104? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE105 | Char | 656 | 659 | Is this console enabled for route code 105? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE106 | Char | 661 | 664 | Is this console enabled for route code 106? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE107 | Char | 666 | 669 | Is this console enabled for route code 107? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE108 | Char | 671 | 674 | Is this console enabled for route code 108? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE109 | Char | 676 | 679 | Is this console enabled for route code 109? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE110 | Char | 681 | 684 | Is this console enabled for route code 110? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE111 | Char | 686 | 689 | Is this console enabled for route code 111? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE112 | Char | 691 | 694 | Is this console enabled for route code 112? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE113 | Char | 696 | 699 | Is this console enabled for route code 113? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE114 | Char | 701 | 704 | Is this console enabled for route code 114? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE115 | Char | 706 | 709 | Is this console enabled for route code 115? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE116 | Char | 711 | 714 | Is this console enabled for route code 116? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE117 | Char | 716 | 719 | Is this console enabled for route code 117? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE118 | Char | 721 | 724 | Is this console enabled for route code 118? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE119 | Char | 726 | 729 | Is this console enabled for route code 119? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE120 | Char | 731 | 734 | Is this console enabled for route code 120? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE121 | Char | 736 | 739 | Is this console enabled for route code 121? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE122 | Char | 741 | 744 | Is this console enabled for route code 122? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE123 | Char | 746 | 749 | Is this console enabled for route code 123? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE124 | Char | 751 | 754 | Is this console enabled for route code 124? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE125 | Char | 756 | 759 | Is this console enabled for route code 125? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE126 | Char | 761 | 764 | Is this console enabled for route code 126? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE127 | Char | 766 | 769 | Is this console enabled for route code 127? Valid Values include "Yes" and "No". |
| USOPR_ROUTECODE128 | Char | 771 | 774 | Is this console enabled for route code 128? Valid Values include "Yes" and "No". |
| USOPR_LOGCMDRESP | Char | 776 | 783 | Specifies the logging of command responses received by the extended operator. Valid values are SYSTEM, NO, and blank. |
| USOPR_MIGRATIONID | Char | 785 | 788 | Is this extended operator to receive a migration ID? |
| USOPR_DELOPERMSG | Char | 790 | 797 | Does this extended operator receive delete operator messages? Valid values are NORMAL, ALL, and NONE. |
| USOPR_RETRIEVE_KEY | Char | 799 | 806 | Specifies a retrieval key used for searching. A null value is indicated by NONE. |
| USOPR_CMDSYS | Char | 808 | 815 | The name of the system that the extended operator is connected to for command processing. |
| USOPR_UD | Char | 817 | 820 | Is this operator to receive undeliverable messages? Valid Values include "Yes" and "No". |
| USOPR_ALTGRP_ID | Char | 822 | 829 | The default group associated with this operator. |
| USOPR_AUTO | Char | 831 | 834 | Is this operator to receive messages automated within the sysplex? Valid Values include "Yes" and "No". |
| USOPR_HC | Char | 836 | 839 | Is this operator to receive messages that are directed to hardcopy? Valid Values include "Yes" and "No". |
| USOPR_INT | Char | 841 | 844 | Is this operator to receive messages that are directed to console ID zero? Valid Values include "Yes" and "No". |
| USOPR_UNKN | Char | 846 | 849 | Is this operator to receive messages which are directed to unknown console IDs? Valid Values include "Yes" and "No". |
User OPERPARM scope (0251)
The user OPERPARM scope record defines the scope of the operator. There is one record per user/OPERPARM scope combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USOPRP_RECORD_TYPE | Int | 1 | 4 | Record type of the User OPERPARM Scope record (0251). |
| USOPRP_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USOPRP_SYSTEM | Char | 15 | 22 | System name. |
User WORKATTR data record (0260)
The user WORKATTR data record defines the logistical information for the user. There is one record per user/WORKATTR data combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USWRK_RECORD_TYPE | Int | 1 | 4 | Record type of the User WORKATTR Data record (0260). |
| USWRK_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USWRK_AREA_NAME | Char | 15 | 74 | Area for delivery. |
| USWRK_BUILDING | Char | 76 | 135 | Building for delivery. |
| USWRK_DEPARTMENT | Char | 137 | 196 | Department for delivery. |
| USWRK_ROOM | Char | 198 | 257 | Room for delivery. |
| USWRK_ADDR_LINE1 | Char | 259 | 318 | Address line 1. |
| USWRK_ADDR_LINE2 | Char | 320 | 379 | Address line 2. |
| USWRK_ADDR_LINE3 | Char | 381 | 440 | Address line 3. |
| USWRK_ADDR_LINE4 | Char | 442 | 501 | Address line 4. |
| USWRK_ACCOUNT | Char | 503 | 757 | Account number. |
User OMVS data record (0270)
The user OMVS data record defines the information required by z/OS UNIX to verify that users are associated with a valid z/OS UNIX user identifier (UID). These records define the UIDs that have been assigned to RACF users, their default directory, default program name, and user limits.
There is only one record per user/UID data combination.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USOMVS_RECORD_TYPE | Int | 1 | 4 | Record type of the User Data record (0270). |
| USOMVS_NAME | Char | 6 | 13 | User name as taken from the profile name. |
| USOMVS_UID | Char | 15 | 24 | z/OS UNIX user identifier (UID) associated with the user name from the profile. |
| USOMVS_HOME_PATH | Char | 26 | 1048 | HOME PATH associated with the z/OS UNIX user identifier (UID). |
| USOMVS_PROGRAM | Char | 1050 | 2072 | Default Program associated with the z/OS UNIX user identifier (UID). |
| USOMVS_CPUTIMEMAX | Int | 2074 | 2083 | Maximum CPU time associated with the UID. |
| USOMVS_ASSIZEMAX | Int | 2085 | 2094 | Maximum address space size associated with the UID. |
| USOMVS_FILEPROCMAX | Int | 2096 | 2105 | Maximum active or open files associated with the UID. |
| USOMVS_PROCUSERMAX | Int | 2107 | 2116 | Maximum number of processes associated with the UID. |
| USOMVS_THREADSMAX | Int | 2118 | 2127 | Maximum number of threads associated with the UID. |
| USOMVS_MMAPAREAMAX | Int | 2129 | 2138 | Maximum mappable storage amount associated with the UID. |
| USOMVS_MEMLIMIT | Char | 2140 | 2148 | Maximum size of non-shared memory |
| USOMVS_SHMEMAX | Char | 2150 | 2158 | Maximum size of shared memory |
User NETVIEW segment record (0280)
The user NETVIEW segment record defines the information required by NetView®.
There is only one record per user profile that contains a NETVIEW segment.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USNETV_RECORD_TYPE | Int | 1 | 4 | Record type of the user NETVIEW segment record (0280). |
| USNETV_NAME | Char | 6 | 13 | User ID as taken from profile name |
| USNETV_IC | Char | 15 | 269 | Command list processed at logon |
| USNETV_CONSNAME | Char | 271 | 278 | Default console name |
| USNETV_CTL | Char | 280 | 287 | CTL value: GENERAL, GLOBAL, or SPECIFIC |
| USNETV_MSGRECVR | Char | 289 | 292 | Eligible to receive unsolicited messages? Valid Values include "Yes" and "No". |
| USNETV_NGMFADMN | Char | 294 | 297 | Authorized to NetView graphic monitoring facility? Valid Values include "Yes" and "No". |
| USNETV_NGMFVSPN | Char | 299 | 306 | Value of view span options |
User OPCLASS record (0281)
The user OPCLASS record defines the information required by NetView.
There is only one record per OPCLASS specified in the NETVIEW segment.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USNOPC_RECORD_TYPE | Int | 1 | 4 | Record type of the user OPCLASS record (0281). |
| USNOPC_NAME | Char | 6 | 13 | User ID as taken from the profile name |
| USNOPC_OPCLASS | Int | 15 | 19 | OPCLASS value from 1 to 2040 |
User DOMAINS record (0282)
The user DOMAINS record defines the information required by NetView.
There is only one record per DOMAIN specified in the NETVIEW segment.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USNDOM_RECORD_TYPE | Int | 1 | 4 | Record type of the user DOMAINS record (0282). |
| USNDOM_NAME | Char | 6 | 13 | User ID as taken from the profile name |
| USNDOM_DOMAINS | Char | 15 | 19 | DOMAIN value. |
User DCE data record (0290)
The user DCE data record defines the non-repeating group information that is contained within the user's DCE segment.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USDCE_RECORD_TYPE | Int | 1 | 4 | Record type of the user DCE data record (0290). |
| USDCE_NAME | Char | 6 | 13 | RACF user name as taken from the profile name. |
| USDCE_UUID | Char | 15 | 50 | DCE UUID associated with the user name from the profile. |
| USDCE_DCE_NAME | Char | 52 | 1074 | DCE principal name associated with this user. |
| USDCE_HOMECELL | Char | 1076 | 2098 | Home cell name. |
| USDCE_HOMEUUID | Char | 2100 | 2135 | Home cell UUID. |
| USDCE_AUTOLOGIN | Char | 2137 | 2140 | Is this user eligible for an automatic DCE login? Valid Values include "Yes" and "No". |
User OVM data record (02A0)
The user OVM data record defines the information required by OpenExtensions. These records define the user identifiers (UIDs) that have been assigned to RACF users, their default directory, default program name, and the file system root.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USOVM_RECORD_TYPE | Int | 1 | 4 | Record type of the user OVM data record (02A0). |
| USOVM_NAME | Char | 6 | 13 | User name as taken from the profile name. |
| USOVM_UID | Char | 15 | 24 | User identifier (UID) associated with the user name from the profile. |
| USOVM_HOME_PATH | Char | 26 | 1048 | Home path associated with the user identifier (UID). |
| USOVM_PROGRAM | Char | 1050 | 2072 | Default program associated with the user identifier (UID). |
| USOVM_FSROOT | Char | 2074 | 3096 | File system root for this user. |
User LNOTES data record (02B0)
The user LNOTES data record contains the Lotus Notes for z/OS information defined in the LNOTES segment of the user's profile.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USLNOT_RECORD_TYPE | Int | 1 | 4 | Record type of the LNOTES data record (02B0). |
| USLNOT_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USLNOT_SNAME | Char | 15 | 78 | LNOTES short name associated with the user ID. |
User NDS data record (02C0)
The user NDS data record contains the Novell Directory Services for OS/390 information defined in the NDS segment of the user's profile.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USNDS_RECORD_TYPE | Int | 1 | 4 | Record type of the NDS data record (02C0). |
| USNDS_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USNDS_UNAME | Char | 15 | 260 | NDS user name associated with the user ID. |
User KERB data record (02D0)
The user KERB data record defines the Kerberos principal information for a user. There is one record per user profile that contains a KERB segment.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USKERB_RECORD_TYPE | Int | 1 | 4 | Record type of the User KERB segment record (02D0). |
| USKERB_NAME | Char | 6 | 13 | RACF user name as taken from the profile. |
| USKERB_KERBNAME | Char | 15 | 254 | The Kerberos principal name. |
| USKERB_MAX_LIFE | Int | 256 | 265 | Maximum ticket life. |
| USKERB_KEY_VERS | Int | 267 | 269 | Current key version. |
| USKERB_ENCRYPT_DES | Char | 271 | 274 | Is key encryption using DES enabled? Valid Values include "Yes" and "No". |
| USKERB_ENCRYPT_DES3 | Char | 276 | 279 | Is key encryption using DES3 enabled? Valid Values include "Yes" and "No". |
| USKERB_ENCRYPT_DESD | Char | 281 | 284 | Is key encryption using DES with derivation enabled? Valid Values include "Yes" and "No". |
| USKERB_ENCRPT_A128 | Char | 286 | 289 | Is key encryption using AES128 enabled? Valid Values include "Yes" and "No". |
| USKERB_ENCRPT_A256 | Char | 291 | 294 | Is key encryption using AES256 enabled? Valid Values include "Yes" and "No". |
| USKERB_KEY_FROM | Char | 351 | 358 | Key source. Valid values are PASSWORD or PHRASE. |
User PROXY record (02E0)
The user PROXY record identifies default information related to the LDAP proxy for a user. There is only one record per user profile that contains a PROXY segment.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USPROXY_RECORD_TYPE | Int | 1 | 4 | Record type of the user PROXY record (02E0). |
| USPROXY_NAME | Char | 6 | 13 | RACF user name as taken from the profile name. |
| USPROXY_LDAP_HOST | Char | 15 | 1037 | LDAP server URL. |
| USPROXY_BIND_DN | Char | 1039 | 2061 | LDAP BIND distinguished name. |
User EIM data record (02F0)
The user EIM record defines the LDAPBIND profile for a user. There is one record per user profile that contains the EIM segment.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USEIM_RECORD_TYPE | Int | 1 | 4 | Record type of the user EIM segment record (02F0). |
| USEIM_NAME | Char | 6 | 13 | User name. |
| USEIM_LDAPPROF | Char | 15 | 260 | EIM LDAPBIND profile name. |
User CSDATA custom fields record (02G1)
The User CSDATA custom fields record defines custom fields associated with a user. There is one record per combination of user and CSDATA custom fields.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USCSD_RECORD_TYPE | Int | 1 | 4 | Record type of the user CSDATA custom fields record (02G1). |
| USCSD_NAME | Char | 6 | 13 | User name. |
| USCSD_TYPE | Char | 15 | 18 | Data type for the custom field. Valid values are CHAR, FLAG, HEX, NUM. |
| USCSD_KEY | Char | 20 | 51 | Custom field keyword; maximum length = 8. |
| USCSD_VALUE | Char | 53 | 1152 | Custom field value. |
User MFA factor tags data record (1210)
The User MFA factor tags data record defines the basic information about a the MFA factor tags data.
| Field Name | Type | Position | Comments | |
|---|---|---|---|---|
| Start | End | |||
| USMFAC_RECORD_TYPE | Int | 1 | 4 | Record type of the user Multifactor authentication factor configuration data record (1210). |
| USMFAC_NAME | Char | 6 | 13 | User ID as taken from the profile name. |
| USMFAC_FACTOR_NAME | Char | 15 | 34 | Factor name. |
| USMFAC_TAG_NAME | Char | 36 | 55 | The tag name associated with the factor. |
| USMFAC_TAG_VALUE | Char | 57 | 1080 | Tag value associated with the tag name. |