Definition of 1A4nD

 

1A4nD INVALID LOGICAL UNIT SPECIFICATION
1A41D INVALID LOGICAL UNIT SPECIFICATION
1A42D INVALID LOGICAL UNIT SPECIFICATION
1A43D INVALID LOGICAL UNIT SPECIFICATION
1A44D INVALID LOGICAL UNIT SPECIFICATION
1A45D INVALID LOGICAL UNIT SPECIFICATION
1A46D INVALID LOGICAL UNIT SPECIFICATION
1A47D INVALID LOGICAL UNIT SPECIFICATION
1A48D INVALID LOGICAL UNIT SPECIFICATION
1A49D INVALID LOGICAL UNIT SPECIFICATION
n indicates the field processed when the error was detected.
Cause: The previous statement contained a logical unit that was invalid. This could result
from:
Format error, or
The number of the unit is higher than the number of LUBs contained in the class. For example,
SYS020 is specified when space has been allocated for 15 programmer logical units, or
The previous ASSGN attempted to assign SYSLNK in a foreground partition with a supervisor
lacking private core image library support, or
SYSVIS or SYSRES is specified at job control time.
System Action: If SYSLOG is assigned to a keyboard, the system waits for an operator
response; otherwise, the invalid statement is ignored.
Programmer Action: Change the logical unit specification in your program, or
Reassemble the supervisor with additional LUB entries, or with private core image library
support.
If the problem recurs, have the supoervisor and program listing available for problem determi-
nauon.
Operator Action: Issue the LISTIO command and use the output to check if the logical unit
specified is valid and then type in the correct logical unit, or
Type CANCEL to cancel job. or
Type IGNORE or press END/ENTER to ignore the statement if you can do without (for
example, if SYSVIS was specified at job control time), and continue processing.
If the problem recurs, have the
· system log
· LISTIO output
available for problem determination.





Used with Courtesy and Permission of International Business Machines, Inc.