Easytrieve SYSUSERID — User ID System Variable

Field Definition and Size

SYSUSERID occupies sixteen bytes of alphanumeric storage in system-defined working storage. That width accommodates eight-character classic userids with room for longer identities or padding on some systems. When copying into report headers, use a working field of at least sixteen bytes or trim trailing spaces with documented string functions if columns are narrow. Do not truncate to eight bytes without verifying downstream audit tools still match RACF logs.

CICS and SCREEN Activities

Online inquiry programs display welcome messages with SYSUSERID—Hello SMITH—and log actions per terminal operator. SCREEN statement field lists may show SYSUSERID as output-only on admin panels. Security reviews verify users see only their authorized data; SYSUSERID helps branch logic when test terminals need different behavior from production users—guarded by proper RACF profiles, not hard-coded userid lists in source when avoidable.

1
2
3
4
5
6
7
8
9
10
11
12
13
SCREEN INQUIRY
  KEY F3 NAME 'Exit' EXIT
 
BEFORE-SCREEN. PROC
  MSG-LINE = 'USER:'
  MOVE SYSUSERID TO SCR-USER-ID
END-PROC
 
AFTER-SCREEN. PROC
  IF KEY-PRESSED EQ F3
     EXIT
  END-IF
END-PROC

Batch Execution Context

Batch SYSUSERID reflects the identity Easytrieve associates with the execution environment— often the TSO userid that submitted the job or a started task identity depending on how JCL was invoked. Scheduler surrogate accounts may show a service id rather than a human name. Document your shop standard: auditors may require both submitter from JES and SYSUSERID from Easytrieve when they differ. When identity must come strictly from JCL, complement SYSUSERID with &SYSUID passed on PARM similar to job name patterns.

Audit Report Headers

Combine SYSUSERID with SYSDATE, SYSTIME, and a captured job name field for SOX-style banners. Place on TITLE 02 or FOOTING so every page carries identity without repeating logic on each LINE. For extract files, MOVE SYSUSERID to OUT-USER-ID on header records written once in START procedure.

1
2
3
4
5
6
REPORT AUDIT-RPT
  TITLE 01 'GENERAL LEDGER EXTRACT'
  TITLE 02 'RUN BY:' COL 1 SYSUSERID COL 20 SYSDATE COL 35 SYSTIME
 
JOB INPUT GLFILE
  LINE ACCT-NO AMOUNT

Migration: Reserved Word Collision

Pre-11.6 programs sometimes defined a field literally named SYSUSERID storing business data—a dangerous name even before reservation. New Reserved Words documentation lists SYSUSERID among terms that break compile in function mode. Rename to WS-USER-ID or AUDIT-USER-ID and recompile all impacted members. Global search source libraries before mass migration weekend.

SYSUSERID Versus TERM-NAME

Screen processing also documents TERM-NAME for terminal identification. User id answers who; terminal id answers which device. Security forensics may need both on violation logs. Do not substitute one for the other on audit designs requiring dual capture.

Privacy and Logging Considerations

DISPLAY SYSUSERID to SYSPRINT on every input record may expose personal identifiers in logs retained years—align with data privacy policy. Prefer header-level stamp. Mask or hash when exporting logs to unsecured ticket systems.

Common SYSUSERID Mistakes

• Using SYSUSERID as a DEFINE field name in new 11.6 programs.
• Assuming batch SYSUSERID always equals RACF log userid without verification.
• Truncating sixteen-byte field to eight on TITLE without audit approval.
• Omitting userid stamp when regulations require three-way header with date and job.
• Confusing SYSUSERID with SQL USER or DB2 authorization id.
• Hard-coding userid tests instead of profile-driven security.

Explain It Like I'm Five

SYSUSERID is your name tag the computer reads when you use a screen program. For batch jobs it is like writing who started the homework machine on the cover page. The name tag is already made—you do not sew your own field called SYSUSERID in 11.6 because that name is reserved for the real tag.

Exercises

1. Add TITLE line with SYSUSERID, SYSDATE, and SYSTIME.
2. Explain CICS EIB copy behavior in your own words.
3. Plan rename for legacy field named SYSUSERID before 11.6 compile.
4. Compare when to use SYSUSERID versus JCL &SYSUID on PARM.
5. Design audit header record layout including sixteen-byte user field.