The Y (Status Interrogate) command displays the status of jobs, tasks, and sessions.
Syntax

Explanation
Y
Returns information about the specified job, task, or session. The information returned depends on the state of the job, task, or session.
The following information is displayed for a job in a queue:
-
Status time
-
Job name
-
Priority
-
Origination information
-
Usercode
-
Limits
-
Timestamp (when queued)
-
Fetch statements
-
Instruction block information
The following information is displayed for a job or task:
-
Status time
-
Program or job name
-
Code file title and creation date
-
Priority
-
Processor set information
-
DMSDelay value (if nonzero)
-
IODelay value (if nonzero)
-
Origination information
-
Originating MCS
-
Usercode
-
Chargecode
-
Accesscode
-
Stack state
For an explanation of stack states, refer to the Task Management Programming Guide
-
RSVP messages
-
Valid replies to RSVP messages
-
DISPLAY messages
-
Display time
-
Checkpoint status, if not null
For information about checkpoint status, refer to the Task Management Programming Guide
-
Title of Program Dump to Disk file
If the mix number identifies a server library, the Y command also returns a list of programs that are linked to the library.
If the mix number identifies a scheduled task, the response includes the number of words required for the task to run.
If the mix number identifies a task waiting on a long tape operation, the response includes the operation. The operations are:
-
Spacing to EOF
-
Locating a block
-
Locating end of data
-
Data security erase in progress
-
Rewinding
The following information is displayed for a session:
-
Status time
-
Station and LSN
-
Originating MCS
-
Usercode
-
Chargecode
-
Accesscode
-
Log-on time
Examples
Example 1
This example shows the response for a job that is waiting on an event:
656 Y
Status of Task 12200\656 at 4:49:39 Program name: *OBJECT/ED ON MCPMAST Codefile created: Monday, June 7, 2004 (2004159) at 16:35:18 Priority: 50 Target Processor Set: 1, Actual Processor Set: 0 Origination: ODT/601/CANDE/1 (LSN 171) MCS: SYSTEM/CANDE Usercode: UC1 Chargecode: 6685 Stack State: Waiting on an event
Example 2
This example shows a response for a job that has a fetch statement:
1555 Y
Job 1555 is waiting in queue 4 at 04:55:08 This job cannot be selected until: The FETCH statement is OK'ed Job name: CANDE/JOB Priority: 60 Origination: Unit 1 Usercode: UC2 CPU Limit: 00:00:03 IO Limit: 00:00:20 Line Limit: 50 Enqueued: Tuesday, June 8, 2004 (2004160) at 04:54:27 This job has an unchecked FETCH statement
Example 3
This example shows a response for a library. It lists the programs that are linked to the library:
1446 Y
Status of Job 1446/1446 at 04:59:55 Program name: *SYSTEM/COMS ON DISK Codefile created: Monday, June 7, 2004 (2004159) at 18:21:09 Priority: 80 Target Processor Set: 1, Actual Processor Set: 0 Origination: Unit 0 Stack State: Frozen, Permanent Display: COMS:PK47 *COMS/INPQ REPLACED ON DISK Displayed Thursday, June 20, 2004 at 14:10:43 This library is being used by 6 programs: 01516: *SYSTEM/COMS/PSH/TTP ON DISK 01515: COMS/PA/FACILITY 01504: MARC 01503: *SYSTEM/MARC/COMMANDER ON DISK 01501: MARC 01487: *SYSTEM/COMS ON DISK
Example 4
This example shows the response for a job that has a specified start time:
9325 Y
Job 9325 is waiting in queue 5 at 15:40:22 This job cannot be selected until: -- The STARTTIME is satisfied Job name: BEGIN JOB;STARTTIME =+1:20; Priority = 50 Origination: Unit 1 Usercode: Limits: None Enqueued: Wednesday, August 4, 2004 (2004216) AT 15:30:13 Starttime: Wednesday, August 4, 2004 (2004216) AT 16:50:00
Example 5
This example shows the response for a job that has completed:
9122 Y
Task 9122 is completed 9120/9122 15:01 P-DS *SC
Example 6
This example shows the response for a job in which the process name and the code file title differ:
9442 Y
Status of Task 16902\5665 at 13:02:59 Program name: (UNX)HUEY Codefile title: (UNX)OBJECT/WY/3 ON SUPPORT Created: Friday, June 11, 2004 (2004162) at 13:00:18 Priority: 50 Target Processor Set: 1, Actual Processor Set: 0 Origination: OCFPIPE17/CANDE/1 (LSN 706) MCS: SYSTEM/CANDE Usercode: UNX Stack State: Waiting on an event
Example 7
This example shows the response for a task with a nonzero CPURATEBIAS:
4218 Y
Status of Task 4210\4218 at 05:13:44 Program name: (ADM)OBJECT/SYMBOL/SOAKER ON USER Codefile created: Monday, January 15, 2007 (2007015) at 11:02:10 Priority: 50 CPURateBias: 0.99 Origination: CCFPORT1/CANDE/1 (LSN 171) MCS: SYSTEM/CANDE ON SYS521 Usercode: ADM Stack State: In Hold Queue
Example 8
This example shows the response for a task with a nonzero DMSDelay value:
4218 Y
Status of Task 4210\4218 at 05:13:44 Program name: (ADM)OBJECT/SYMBOL/SOAKER ON USER Codefile created: Monday, January 15, 2007 (2007015) at 11:02:10 Priority: 50 Target Processor Set: 0, Actual Processor Set: 0 DMSDelay: 0.0067 Origination: CCFPORT1/CANDE/1 (LSN 171) MCS: SYSTEM/CANDE ON SYS521 Usercode: ADM Stack State: In DMS Hold Queue
Example 9
This example shows the response for a task with a nonzero IODelay value:
4218 Y
Status of Task 4210\4218 at 05:13:44 Program name: (ADM)OBJECT/SYMBOL/SOAKER ON USER Codefile created: Wednesday, February 28, 2007 (2007059) at 05:11:10 Priority: 50 Target Processor Set: 0, Actual Processor Set: 0 IODelay: 0.0042 Origination: CCFPORT1/CANDE/1 (LSN 171) MCS: SYSTEM/CANDE ON SYS521 Usercode: ADM Stack State: In I/O Hold Queue
Example 10
This example shows the response for a session:
47077 Y
Status of Session 47077 at 16:09:29 Origination: CCFPORT1/CANDE/1 (LSN 172) MCS: SYSTEM/CANDE Usercode: ADM Logon Time: Tuesday, December 11, 2007 (2007345) at 15:42:37