SFMxSCMB

/DISPLAY,T=?

Changed: row 21, col 41, added text "or TCP/IP"

If entered through batch, this position has TCP/IP information.

SFMxSCMX

/DISPLAY,ST=CA7

Changed to mixed case
Added, row 03, col 35: Level: r11.3 0000
Added, rows 05 – 07, col 41: Information about the System State Manager Interfaces (ARM, OPS/MVS SSM, and Health Checker)
Added, row 08, col 41: CA 7 TZ Offset : zhh:mm
Added, row 09, col 41: TZDISPLAY Value: xxxx
Added, row 10, col 41: TZPREDS Value : xxxx
where z is the sign, and xxxx is either EXEC or CA7.
Added, row 11, col 02: TCP/IP Host Name
Added, row 11, col 51: Port
Added, row 12, col 2: TCP/IP Host Address

/DISPLAY,ST=SEC

Added, row 7, column 29. Option (Other/Propagate)
Added, row 7, column 71, Mixed password indication
Added, row 8, column 71, Command Resource class name
Added row 11, column 2, Bypass Security settings if present
Added, row 13, col 51: AGENT
Changed: row 16, col 51, under User ID Hierarchy, now have two columns, one for JCL and one for Agents
Added, row 20, col 02: MULTIPLE JOBCARDS

/DISPLAY,ST=XPS

Added rows 20-22, column 2, Agent status information

SFMxSLIA

LJOB
LJOB,JOB=
LJOB,LIST= {SCHD|ALL}

If the job last-run date/time is normalized to the EXEC time zone, there is a “+” in column 70. With the JOB= parm, a new line has been added in the blank line before the OWNER= line, starting in column 8:

. LAST RUN: CA 7=yy.ddd hh:mm:ss EXEC=yy.ddd hh:mm:ss EXEC TZO=zhh:mm

where z is the sign.

If LIST=ALL or LIST=SCHD is specified, and the job has a resolved schedule, a new line will appear on the screen under the "---- SCHEDULES ----" line:

LAST RESOLV ON yy.ddd AT hh:mm

where yy.ddd is the Julian date and hh:mm is the hours and minutes the schedule was resolved.

SFMxSLIB

LDSN

A new line has been inserted after the LAST MAINTENANCE ON line. The line starts in column 8, and the text depends on whether the EXEC time zone matches the CA 7 time zone. If they are equal, the line reads as follows:

. LAST CREATED D/T: yy.ddd hh:mm:ss

If they are different, the line reads as follows:

. LAST CREATED: CA 7=yy.ddd hh:mm:ss EXEC=yy.ddd hh:mm:ss EXEC=zhh:mm

where z is the sign.

SFMxSDM0

DB Menu

Changed, row 07, col 09, from "10" to "A"

SFMxSLID

LCTLG

A new column heading, TZO, starts in column 12 on the same row with DATE, TIME, and GDG#. The time zone offset is displayed for the most recent generation only of the data set starting in column 10 in the zhh:mm format, where z is the sign. The time column expanded from hhmm to hhmmss. If the date/time is normalized to the EXEC time zone, column 35 contains a “+”.

Note: If the most recent generation is normalized, it is assumed that all generations are normalized.

SFMxSLIF

LQ

If job start date/time (not the submit date/time) is normalized to the EXEC time zone, column 36 contains a “+”.

SFMxSLIG

LSCHD,LIST= BYSID

To this dynamically built screen, a new line added after the “Last Maintenance” and before “---SCHEDULES---” contains the last resolved date for this job. The added line contains the following:

.LAST RESOLV ON yy.ddd AT hh:mm

SFMxSLIR

LPRRN, LRLOG

If job start and complete date/times are normalized to the EXEC time zone, columns 32 and 52 contain a “+”.

SFMxSLIV

LQ,LIST=JOBX

If job start/end date/times are normalized to the EXEC time zone, column 49 contains a “+”.

SFMxSM80

SCHDMOD

Added, row 07, col 49: LAST RESOLV

SFMHQM50

Restart screen

Added, row 03, col 67: CA 11
Added, row 04, Col 53: JNODE

SFMHSM80
DB.2.7

SCHDMOD

The following new field, LAST RESOLV, is added at row 07, column 48:

LAST RESOLV: yy.ddd AT hh:mm

The new field displays with information after a resolve has been done under CA Workload Automation SE r11.3.