OS/400 Messages

Are you looking for the description of OS/400 (System i) messages e.g. CPF9801? Then you have come to the right place. Below you can see a (hoefully) complete list of of all OS/400 messages with all “second level texts”.

Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

Complete OS/400 Messages Documentation From ALP4004 up to ALX00D6

Complete OS/400 Messages Documentation From ALP4004 up to ALX00D6

This documentation is copyright by IBM.
Count: 1401 Skipped: 0
OS/400 Messages
Degraded voice server availability
Error rate threshold exceeded
Congestion experienced on call setup
DASD media
Optical disk
ID recording surface
Device not available
Device not available
Input device
Selector pen
MICR reader/sorter
Magnetic stripe reader
ID card reader
Optical document reader
Output device
Printer cassette
Input/output device
DASD device
Diskette device
Optical disk device
Tape drive
Touch-sensitive screen
Encryption device
Media library device
Library manager hardware
Library vision system
Disk drive electronics
Envelope depository
Check depository
Card depository
Document depository
Document dispenser
Ticket dispenser
Key dispenser
Coin dispenser
Envelope dispenser
Self-service terminal
Personal banking machine
Teller assist unit
Security problem
Audible alarm
Protective door
Security procedure
Bindery files closed
Partner not authenticated
Local system operator
Remote system operator
Network operator
System programmer
Customer personnel
Service representative
Resource administrator
Printer operator
Terminal control unit operator
LAN bridge operator
LAN manager operator
LAN trace tool operator
File server user
Logged in users
Storage configuration
Work station configuration
Communication configuration
Customization image
Server configuration
LAN configuration table
LAN bridge table
Configuration object not in valid state
Incorrect name specified
Out of resources
Critical resource redefined
Domain name changed
Communication link type changed
Bridge unlinked
Configuration database
File directory structure
Disk partition too small
File server account system file
Domain controller account system file
SNA pass-through group does not exist
SNA pass-through configuration mismatch
Wireless network configuration
Inconsistent bridge configuration data
Origin configuration
Destination configuration
Target resource ID
Source resource ID
Local traffic ID not in range
Destination local traffic ID
Origin local traffic ID
Local traffic ID not provided
Quality of service record not provided
Origin to destination parameters
Destination to origin parameters
Quality of service value inappropriate
Traffic type mismatch
Bandwidth change not allowed
Path change not allowed
Invalid or unrecognized numbering plan
Bandwidth not specified or incorrect
Invalid quality of service
Resource already in use
DLCI not configured
VPC not configured
VCC not configured
Set up information not provided
Required maximum packet size invalid
Configuration parameter mismatch
Duplicate node identifiers
Invalid network identifier
Duplicate roots detected
Resource administratively locked
Duplicate connection name
Traffic type
Address registration
Maximum VPI bits exceeded
Maximum VCI bits exceeded
Maximum VPCS exceeded
Maximum VCCS exceeded
VPC in use
VCC in use
Device or component in test mode
Database information mismatch
Network interface device configuration
Default parameters are incorrect
Incorrect time settings
Software license management
License usage threshold exceeded
License usage limit reached
License usage limit exceeded
License usage limit may violate contract
Monitored event
Unexpected error
Review event detail for probable cause
Perform problem determination procedures
Run on-line problem determination
Invoke intensive mode recording
Determine the reason for the line shutdown
Determine the reason for the loop shutdown
Perform SNA data stream problem determination procedures
Use microcode dump and system procedures to create an APAR
Perform remote modem problem determination
Perform remote DSU/CSU problem determination
Perform outbound line problem determination
Perform inbound line problem determination
Determine resource name of the other remote node
Run modem self test with wrap plug from keypad
Run DSU/CSU self test with wrap plug from control panel
Run modem and line status test
Run DSU/CSU and line status test
Run line test
Run line analysis test
Run transmit/receive test
Run remote node test
Run remote node-DCE interface wrap test
Investigate interference from other port on local modem, if fan-out installed
Review modem and line status data
Run verify command
Review user's disk storage usage
Review statistics associated with the link
Determine reason for remove command
Identify the other contending network node
Determine which network node is at fault
Run line test with wrap plug
Perform transmission line problem determination procedures on &1
Review &1
Perform remote &1 problem determination
Run &1 self test with wrap plug from control panel
Run &1 and line status test
Test route between alert sender and &1
Perform problem determination procedure for &1
Perform problem determination procedure at the reporting location for &1
Run the following at the reporting location
Perform &1 problem determination via a remote console session
Run self test with wrap plug on &1 remote modem and &2 local modem from modem keypads
Run self test with wrap plug on &1 remote DSU/CSU and &2 local DSU/CSU from DSU/CSU control panels
Run self test with wrap plug on &1 remote modem (from keypad) and &2 local DSU/CSU (from control panel)
Run self test with wrap plug on &1 remote DSU/CSU (from control panel) and &2 local modem (from keypad)
Run DSU/CSU and line status test on &1 and &2
Run DCE and line status test on &1 and &2
Perform problem determination procedures at &1 &2
Perform &4 problem determination procedures
Verify X.25 subscription number
Verify adapter address definition
Verify telephone number
Check for correct microcode fix
Request verification of management server reporting links
Check remote node for TC active
Check other remote node for TC active
Check remote node for RTS active
Check other remote node for RTS active
Check configuration of the sending node
Check configuration of the sending node and of the modems
Check configuration of the sending node and of the DSU/CSU's
Check configuration of the remote node
Check for configuration mismatch between application control block and card number
Check configuration of the other remote node
Check configuration of the remote node and remote modem
Check RTS generation parameter
Verify that the fan-out feature is installed
Verify that remote node provides the DCE external clock
Check file directory structure
Review memory usage
Verify application program lock usage
Check for configuration mismatch between application control block and program
Check for configuration mismatch between resource directory and tables and queues definition file
Check processes in message memory pool
Check processes in co-processor message memory pool
Check processes in work memory pool
Verify access authority
Verify adapter installation
Verify destination resource is defined
Verify destination resource is defined in resource directory
Verify application program directory search usage
Identify offending software component
Verify destination resource is valid
Review software component memory usage
Verify destination resource name
Verify command
Verify communication access control block configuration
Verify communication path is working
Verify communication protocol program is working
Verify communication path definition
Verify control block type
Verify control node is active
Verify correct memory image file specified in command
Verify destination node is active
Verify file is defined
Verify size of memory pools
Verify file path
Verify file exists and is not in use
Check communication driver configuration file
Verify file was created with file support
Verify file is valid
Verify file support is started
Verify destination resource server name
Verify destination server is defined
Verify device configuration
Verify device data management support is operating correctly
Verify device name is valid
Verify directory request
Verify originator resource is defined in resource directory
Verify originator resource is defined in subnet configuration
Verify memory location and correct if necessary
Verify originator resource is defined in system configuration
Verify originator resource is started
Verify originator resource is valid
Verify line name
Verify logical address is defined
Verify manufacturing automation protocol is loaded
Verify maximum message size in node information block
Verify message file is defined
Verify message is defined
Verify minidisk request
Verify originator resource is defined
Verify destination resource is stopped
Verify security subnet configuration for control node
Verify application initialization/shut-down sequence
Verify server resource is defined
Verify server resource is valid
Verify logon panel is defined in operator interface panel library
Verify originator resource name
Verify parameter
Verify physical resource is defined
Verify program is loaded
Verify queue number is valid
Verify remote node is active
Verify remote device is varied on
Verify video control block is valid
Verify subnet configuration is valid
Verify subservient node is active
Verify configuration file
Verify system configuration is valid
Verify table distribution group exists on node where failure occurred
Verify table is defined
Verify tables and queues definition file
Verify task number
Verify video control block is defined
Verify back-up D-channel operation
Review server audit trail
Check size and change if set too low
Increase user account limitation
Review server error log
Check domain controller
Check for correct load module
Check configuration of SNA pass-through devices in reporting and adjacent nodes
Check for other messages about the failing device or group
Check for messages about links to other nodes.
Verify connection target information
Verify connection source information
Verify connection setup information
Verify impending event should occur
Check for system contention
Check DASD subsystem unit environment for excessive temperature
Verify logical path
Check channel state
Check DSU/CSU configuration
Check DSU/CSU control panel
Verify that the following contact was made
Verify connection information at destination
Verify connection information at origin
Verify directory information for resource
Check fans
Check ambient air temperature
Verify that wrap plug is installed
Check connection path status
Check connection state
Verify SNA pass-through group name is valid
Verify correct license usage limit
Update license usage limit
Verify consistency of the information in the configuration database
Check status and activate required resource
Verify security configuration at both nodes.
Call &1 and check voice recording
Verify &1
Verify &1 in resource directory
Verify &1 is defined
Verify &1 is defined in subnet configuration
Verify &1 is defined in system configuration
Check for configuration mismatch between system configuration file and &1
Verify &1 is varied on
Verify &1 was created
Verify &1 is accessible
Check configuration of the sending node and of the &1
Verify the current exposure using &1. at the reporting location
Verify security configuration at alert sender and at &1
Check for configuration mismatch between the &1 remote modem and &2 local modem
Check for configuration mismatch between the &1 remote modem and &2 local DSU/CSU
Verify configuration of &1 and &2
Verify &1 &2 &3
Verify &4 is running
Check power
Check power control mode
Check power cord
Check fuses
Check main AC power supply
Check for damage
Check cable and its connections
Check cables and their connections
Check physical installation
Check tape path to read/write head for obstruction
Check uninterruptible power supply
Run appropriate test
Run console test
Run console link test
Run modem tests
Run adapter test
Run ATM loopback test
Run appropriate trace
Run communication line data trace
Obtain dump
Transfer and print MOSS dump
Transfer and print control program dump
Transfer and print line adapter dump
Transfer and print channel adapter dump
Transfer and print token ring coupler dump
Dump control program
Dump channel adapter microcode
Dump line adapter microcode
Dump MOSS microcode
Dump token ring coupler
No action necessary
If SNBU just disconnected then ignore
Retry at originating node will be successful when resource becomes available
If this was an authorized increase no action is necessary
Communications problem bypassed by automatic switch to alternate route
No action necessary, since automatic reset was performed
No action necessary -- automated recovery in progress
Control node &1 now responding
Application &1 now responding
Print server &1 now responding
Perform problem recovery procedures
Refer to operator's guide for corrective action
Follow local backup procedure
Perform loop problem recovery procedures
Perform LAN problem recovery procedures
Perform disk file error recovery procedures
For single drive failures, move pack to another drive and rerun same job
Request reset of ring error monitor component
Request reinitialization of LAN manager
Attempt to reopen the adapter after 30 seconds
Reorganize the file
Leave the additional workstation powered off
Power off another workstation attached to this controller
Transfer the additional workstation to another controller
Locate and eliminate the source of electrical interference
Change registration name of one of the communication control blocks
Reduce amount of auxiliary storage used
Increase amount of auxiliary storage available
Increase amount of main storage available
Power off remote modem
Power off remote DSU/CSU
Power off then power on auto-call unit
Reduce the number of lines/devices attached to the subsystem
Install additional memory
Install additional file servers
Purge unused files
Print then clear error log
Print then clear audit log
Delete second application control block for monitor
Reduce types of audit entries logged
Correct logical device interface procedures (LDIP) problem
Create application control block for inbound server
Increase storage media capacity
Create application control block for outbound server
Create communication control block for communication access control block
Create table distribution group table
Delete jobs
Correct configuration to enable data transparency in node information block
Correct configuration to enable security in node information block
Increase number of task numbers
Increase number of timers
Increase size of control block memory pool
Increase size of driver buffer
Give control of one communication control block to another communication access control block
Halt destination resource
Increase amount of virtual storage available
Increase buffer allocation in line control block
Increase timeout value in line control block
Unload dependent software programs then unload indicated program
Unload offending software component
Increase timeout value in request
Increase size of message memory pool
Increase size of co-processor control block memory pool
Increase size of co-processor message memory pool
Increase size of co-processor work memory pool
Increase size of resource
Increase size of work memory pool
Terminate user session
Increase timeout value in application control block
Increase timeout value in database control block
Release all locked records
Synchronize passwords at file server and domain controller
Open resource
Synchronize system clock times
Log off low priority users
Resolve in-doubt logical units of work
Release locked member
Print jobs
Use device data management support help facility for more information on return codes
Select valid memory pool
Select valid parameter
Use another database control block
Select valid request size
Stop then start line control block
Stop printer control block
Stop printer control blocks not in use
Stop then start device control block
Delete file
Rename file
Load communications subsystem controller
Load co-processor dispatcher
Decrease request size
Reduce number of applications executing
Resize and copy file
Close any files which are not in use
Free space on designated disk drive
Re-create file
Restore or reset file
Remove processes from system
Delete members from table or queue
Disconnect from database then connect to another database
Disconnect from database then connect to another database
Increase network control blocks for network driver
Format fixed disk
Install fix for current problem, if available
Delete dynamically added resources (PUs, LUs, and sessions)
Ensure that access is authorized for attempted use of problem resolution facility
Wait for fix - problem recorded - resolution under study
Install fix sent for reported known problem
Adjust if necessary
Clean tape drive
Replace power supply
Restore main AC power supply
Attempt to reopen the adapter after 30 seconds with alternate speed
Increase network capacity to carry more connections
Increase connection bandwidth
Increase port bandwidth
Increase machine resource capacity
Reduce number of active connections
Set system clock time parameters to correct values
Restore &1 from backup
Perform &1
Follow problem recovery procedure indicated at printer for &1
Follow problem recovery procedure indicated at printer server for &1
For corrective action refer to &1
Review &1 and update as required
Create new &1
Restore &1 on domain controller and file server from backup file
Stop &1
Follow problem handling procedures for &1
Power off then power on &1
Restore &1 licensed internal code
Save &1
Run &1 and mirror the drive
Run &1 and recover detached secondary
Run &1 and correct all errors
Power off remote &1
Delete journal &1 connection name &2
Initialize journal &1 connection name &2
Re-create journal &1 connection name &2
Run &1 on file contained in &2
Increase the value of &1 &2
Decrease the value of &1 &2
Stop &4
Vary offline
Move the paging data sets to another subsystem
Move pack to another drive and rerun the same job
Restart job
Attempt to reestablish the connection
Rerun the application program
Wait then retry
Retry -- Dial number manually
Retry request
Retry at the original requesting node
Retry job on alternate drive or path
Retry after
Correct then retry
Ready the device then retry
Reset print spooler control file
Reset value within the valid range
Correct node information block configuration
Reactivate B-channel resource
Release held jobs then retry
Correct then retry at original requesting node
Move tape to compatible tape drive
Verify that air vents are not covered
Check for dirty filter
Check cable connection and retry
Activate port then retry
Enable line then retry
Reactivate line
Clear connections
Correct then retry offending software component
Correct connection setup information and try again
Activate one or more ports in the rotary group associated with &1
Activate resources attached to &1
Deactivate resources attached to &1
Repeat call with &1
Run &1 and verify drive
Run &1 and verify mirrored drive(s)
Check &1 volume status
Re-IPL the communication controller
Re-IPL the secondary finance controller
Re-IML the control unit
Reactivate LAN management server program
Follow alert sender's procedures for resource activation
Activate the session
Restart device data management support
Restart device data management support server
Restart distribution server
Restart print spooler
Restart printer control block
Restart communication protocol program
Restart destination server
Restart program
Resume operation on backup PU
Restart communications subsystem controller
Restart resource
Resume destination resource
Resume resource
Start communication control block
Start destination resource
Start device data management support server
Start disk queue server
Start file support
Start inbound server
Start only one communication control block at a time
Start outbound server
Power on or restart
Stop / restart server logon service
Restart software subsystem
Restart software subtask
Restart message logging
Restart server
Restart resource when incident resolved
IPL the system at the reporting location
When convenient, manually deactivate then reactivate resource
Vary or connect &1 online
IML the &1
Activate &1
Start &1
Restart &1
IPL &1 from &2 with &3
Restart &4
Correct installation problem
Correct generation problem
Correct customization parameters
Correct configuration
Apply correct software level
Load the required optional module
Increase intervention timer value
Correct address from modem keypad
Correct address from DSU/CSU control panel
Enable LPDA-2 from modem keypad
Enable LPDA-2 from DSU/CSU control panel
Configure modem
Configure DSU/CSU
Configure local modem as primary or control
Configure local DSU/CSU as primary or control
Check threshold limit and change if set too low
Correct the address
Check threshold limit and change if set too high
Change call setup parameters
Update client application program to provide password encryption
Change server configuration to accept unencrypted passwords
Check lower limit and change if set too high
Install latest microcode level
Apply latest service level
Increase number of control blocks in genned pool
Increase number of users in IEEE 802.2 profile
Increase number of SAPS in IEEE 802.2 profile
Increase maximum number of connections allowed on this node
Add destination resource to resource directory
Add originator resource to subnet directory
Add originator resource to system configuration
Add resource to table and queues definition file
Add destination resource to control block file
Correct appropriate configuration parameters
Perform online configuration and update configuration database
Change default configuration parameters to appropriate values
Define resource to system
Remove resource from application definitions
Set problem resolution facility flag on for resource
If this was an unauthorized increase then do the following
Change the license usage limit back to the authorized limit
Disconnect one network node from the network and give it a new CP name
Add &1 to resource directory
Add &1 to subnet configuration
Add &1 to system configuration
Configure local &1 as primary or control
Configure &1
Correct address from &1 control panel
Enable LPDA-2 from &1 control panel
Increase &1 on &2
Replace media
For removable media, change media and retry
Place backup diskette in drive
Change diskette and retry
Put correct paper in cassette
Put cassette in printer
Add paper
Replenish supplies
Replace ribbon
Add ink
Add toner
Change all air filters
Add fuser oil
Add staples
Replace defective equipment
Replace keyboard
Replace module
Replace card
Replace device
Replace battery
Replace printer
Replace display control module
Replace MSR or MSRE
Replace storage controller
Replace workstation controller
Replace communications subsystem controller
Replace the card identified by &1
Replace cable identified by &1
Replace &1
Replace the battery identified by &1 &2
Perform problem bypass procedures
Replace modem
Replace DSU/CSU
Change to backup speed
Activate SNBU, if available
Disconnect and re-dial SNBU line
Use alternate port or line
Backup the drive at server
Remove the faulty network node from the network
Quiesce and move the &1 workload to another system
Perform manual fallback to &1
Remove &1 from service and resume operations if possible
Backup, reformat, and restore
Backup data before powering off
Remove media
Remove documents
Remove cards
Prepare for server shutdown
Prepare for automatic system shutdown
Reply to message
Reply to outstanding message
Inactivate or disable
Inactivate force resource
Review alert detail
Report alert detail
Review most recent traffic statistics
Review link detailed data
Review hexadecimal display of the alert record
Review associated resources
Review supporting data
Review recent alerts for this resource
Review recent statistical records for this resource
Review correlated alerts
Review recent alerts from other nodes for the same problem and related alerts from the reporting node.
Find original requesting node - review recent alerts for SNA pass-through errors with &1 as alerted resource
Review recent alerts for &1 &2
Review data logs
Review remote device logs
Review device statistical log at alert sender
Review supporting data at alert sender
Review network log at alert forwarder
Rely on accounting data from remote connection partner
Review problem resolution facility status
Review messages for &1 at the alert sender
Review sending device log
Review partner's recovery log --
Review job log &1/&2/&3
Contact appropriate service representative
Contact consumer service representative
Contact security control representative
Contact service representative for list of remaining part numbers
Place service call to retain if the RETAIN service is supported
Place service call to appropriate service representative
Dial &1 and report the machine information
Call &1 from designated phone
Provide remote service call authorization for &4
Contact service representative for &4
Contact administrative personnel
Contact token-ring administrator responsible for this LAN
Contact CSMA/CD administrator responsible for this LAN
Contact LAN administrator responsible for this LAN
Contact network information service for private network called
Contact X.21 network information service
Contact ISDN network information service
Contact X.25 network information service
Contact relational database administrator
Contact personnel responsible for connection to ISDN network
Contact server administrator
Contact network administrator
Contact administrator of affected resources
Contact DS1 network information service
Contact personnel responsible for connection to DS1 network
Contact communications systems programmer
Contact operator responsible for alert sender
Contact systems programmer
Contact personnel responsible for DASD support
Contact NBBS network administrator
Contact frame relay network administrator
Contact ATM network administrator
Contact personnel responsible for connection to DS3 network
Contact printer operator
Contact terminal control unit operator
Contact called DTE's operator
Contact remote DTE's operator
Contact PBM network operator
Contact remote link station operator
Contact calling DTE's operator
Contact software provider to authorize increase
Contact the software provider if an increase is necessary
If required, query &1 at &2 about &3
Contact systems administrator for &4
Report the following
Report the following
Report the following
Report the following
Report the following logical unit of work identifer
If problem recurs then do the following
If problem persists then do the following
If problem continues to occur repeatedly then do the following
If unsuccessful then do the following
Wait for additional message before taking action
Expect a call from the service organization to provide an estimated time of arrival
Refer to product documentation for additional information
Refer to modem documentation for additional information
Refer to industrial computer extensions library for additional information
Refer to &1 for additional information
Refer to &4 product documentation for additional information
Correct installation problem
Multiple failures indicate channel failure
Multiple failures indicate controller failure
Multiple drive failures on same controller indicate controller failure
Multiple failures indicate control unit failure
Multiple failures indicate terminal multiplexer failure
Recurrence of same error indicates media failure
Recurrence of problem indicates device or attachment error
Recurrence indicates media problem
No recurrence of failure indicates original drive failure
Multiple failures indicate line adapter multiplexer failure
Do one of the following
Notify user
High error rate between the following nodes
Link failure between the following nodes
Link connected to the following node failed
Other node in the link is one of the following nodes
No further action required unless problem persists
This alert identifies the cause of a previous error which has been recovered
Service can be scheduled at a later time unless repeated failures prevent normal operation
Resume operation
Heuristic damage
Coordinator committed
Coordinator backed out
Agent committed
Agent backed out
Agent in-doubt
DASD HDA power sequence fault
Additional analysis (by service personnel) is required to determine repair impact
Repairing redundant equipment will not cause a loss of function
Repair will disable protocol converter
Exception on protocol converter
Automatic adapter (re)initialization attempted
Resources have been lost, but they could not be specifically identified
Format error
Protocol error
Link incident analysis in progress
Link connected to the following node has a high error rate
Record may be incorrect in the topology database, but will be corrected automatically within one hour
No IML capabilities
IPL capabilities limited
No IPL capabilities
Normal operations can continue but if auxiliary storage is exhausted onsite action will be necessary
To recover lost resource
Data is not available from main or auxiliary storage
Data is available from auxiliary storage
Data from all other tracks is available from auxiliary storage
Probable temporary power source disruption
Mirrored device
Dynamic sparing initiated
After successful completion
Condition may reflect normal operations - for example, termination of a dial-up connection
A service call has been automatically placed to RETAIN
For &1
&1 has been restored from backup file
No backup available for &1
Node &1
Coordinator &1
&1 unsuccessful access attempts
&1 degraded
&1 disabled
&1 enabled
Contending TDU received from adjacent network node &1 - TDU may not have originated from this node
Incorrect TDU information
Network node record being contended over is &1
Transmission priority for subnet &1 is &2
DASD cache exception -- &1 &2
Failing component location
Origin node data
Destination node data
Node data
Media exception on &1 &2 &3
Additional data -- &1 &2 &3
DASD control unit exception on &1 &2 &3
Repair will disable &1 &2 &3
Device exception on &1 &2 &3
Affected resource is identified by &1 &2 &3
And &1 &2 &3
TG record being contended over is &1, from &2 TO &3
For &4
Prepare for automatic shutdown of &4
Node &4
For &5
Resource associated with the alert condition is &5
Permanent loss of availability
Temporary loss of availability
Operator intervention required
Permanently affected resource
Impending problem
Redundancy lost
Situation event
Storage capacity exceeded
Insufficient storage media space
Insufficient memory
The portion of main storage made available by the user for a particular operation has been exhausted
A user-specified threshold, indicating that available auxiliary storage is nearly full, has been reached
Dynamic allocation of a control block failed
Power off
Local DCE power off
Remote DCE power off
Local digital data device power off
Remote digital data device power off
Local modem power off
Remote modem power off
Local link diagnostic unit power off
Remote link diagnostic unit power off
Remote device power off
Local terminal adapter (TA) power off
Remote terminal adapter (TA) power off
Local controller power off
Remote controller power off
Printer power off
Communication equipment power off
Calling DCE power off
Called DCE power off
Called DTE power off
Modem power off
Terminal multiplexer power off
Local NT1 power off
Service processor power off
Device power off
Console power off
LAN manager power off
Remote node power off
Local DSU/CSU power off
Remote DSU/CSU power off
Optical fiber converter power off
Server has been powered off locally, with the switch on the front panel
&1 local modem power off
&1 remote modem power off
&1 local DSU/CSU power off
&1 remote DSU/CSU power off
&1 local &2 power off
&1 remote &2 power off
Remote node
Called DTE taken out of service
Remote node control program IPL has occurred
Connection not established
Called number busy
Incorrect network service access point called
Access to called network service access point not activated
Incorrect telephone number specified
Incorrect call user data
New telephone number assigned to called DTE
Incorrect parameter specified
Calling DTE does not subscribe to this facility
User classes of service incompatible
Service or subscription parameter error
X.21 connection intentionally cleared by terminal control unit operator
Incomplete or malformed call setup message
Facility parameter invalid or not supported
Logical path not established
Connection not established:
Incorrect telephone number
Incorrect memory address -- &1
Invalid modem command -- &1
Called number busy -- &1
Connection not established for &1
Service call cannot complete for &1
The maximum number of workstations supportable by the local workstation controller has been exceeded
The maximum number of users supportable by the server has been exceeded
Maximum number of lines allowed already in use
Associated SNA pass-through device already in session with another device
Line not enabled
Port deactivated
Link not enabled
Line not enabled at called DTE
Port deactivated at called DTE
Line not varied on
Adapter not ready
An operator has deactivated all ports in a rotary group
An operator has deactivated all ports in a rotary group used by an X.21 short hold mode session
Adapter &1 awaiting download
Cable not connected
Cabling installed incorrectly
Keyboard unplugged
Line switched to incorrect position
Device cable not connected
Cable not connected:
Cable not installed:
Cable unplugged:
SNBU has been disconnected
TC lead active on remote node interface
TC lead active on other remote node interface
Remote DSU/CSU in test mode
Speed mismatch between modems on &1
Speed mismatch between DSU/CSU's on &1
&1 local modem in test mode
&1 local DSU/CSU in test mode
&1 remote modem in test mode
&1 remote DSU/CSU in test mode
&1 local modem reinitialized
&1 local DSU/CSU reinitialized
&1 local DSU/CSU detected DDS loopback active in the last 2 minutes
&1 remote DSU/CSU detected DDS loopback active in the last 2 minutes
&1 local modem power off then on
&1 remote modem power off then on
&1 local DSU/CSU power off then on
&1 remote DSU/CSU power off then on
&1 remote DSU/CSU in configuration mode
&1 local DSU/CSU in configuration mode
&1 local DSU/CSU in loopback mode
&1 local &2 in test mode
&1 remote &2 in test mode
&1 local &2 detected network loopback test
&1 remote &2 detected network loopback test
&1 local &2 powered off then on
&1 remote &2 powered off then on
&1 remote &2 in configuration mode
Performance degraded
Storage subsystem overloaded
Work station subsystem overloaded
Communication subsystem overloaded
Media defective
Improper diskette inserted
No diskette or defective diskette inserted
Non-duplex paper in cassette
ID card recording surface
Media jam
Card jam
Forms jam
Paper jam
Film jam
Media supply exhausted
Out of cards
Out of forms
Out of paper
Out of film
Out of bills or documents
Out of envelopes
Cassette out of paper
Out of supplies
End of ribbon encountered
Out of ink
Out of toner
Out of fuser oil
Out of staples
Media supply low
Low on cards
Low on forms
Low on paper
Low on film
Low on bills or documents
Low on envelopes
Low on supplies
Low on ink
Low on toner
Low on fuser oil
Low on staples
Device not ready
Device offline
Remote device offline
DASD device not ready
Diskette not ready
Tape not ready
Printer not ready
Bin cover open
Printer door open
Output hopper full
Telephone set not in data mode
Remote node offline
Remote node reinitialized
Domain controller stopped or powered off
Service door open
Modem not in data mode
Local modem powered off then on
Depository nearly full
Depository full
Operator intervention required
No cassette in printer
Cartridge not installed correctly
Out of focus
User needs assistance
Device is not in the proper position
Network operator
Call authorization required
Address compare detected on &1
Address compare stop on &1
Service call authorization required for call type &1
Incorrect procedure
Token-ring remove adapter command received
Paper installed incorrectly
LAN manager operator entered incorrect password
Unauthorized access to LAN management server attempted
Unauthorized user attempted insertion into LAN
Adapter address not entered in authorization list
CSMA/CD remove adapter command received
Operator entered incorrect password
LAN bridge operator took bridge off line
LAN manager operator took bridge off line
User incapacitated LAN management server program
Unauthorized trace tool in LAN
Adapter not at expected address
Authorization list contains incorrect time and day entries
Incorrect address assigned
Local X.25 procedure error
Remote X.25 procedure error
Destination resource not open
Invalid control block type
Manufacturing automation protocol not started
Invalid/incorrect specification of originator resource
Printer control block stopped and purged
User has another table member locked
Maximum number of operating system files already open
Maximum number of printer control blocks already started
Maximum number of resources already started
File server password changed
Difference between system clock times unacceptable
Partner restarted without recovery log information
Log name mismatch
Inconsistent heuristic decision
Incorrect test tool used
User's logon time limit exceeded
Already activated by another user
Unauthorized user attempted insertion into wireless network
Incorrect tape loaded
Incompatible compaction algorithm
Multiple adapters attached to one lobe
Telephone answered by other than communications equipment
Printer already started under another printer control block
Task already loaded
Operator deactivated the session
Operator took program offline
Network interface not varied on
Controller description object not varied on
Resource not available
Resource not available at an intermediate node
Local ISDN procedure error
Remote ISDN procedure error
Local procedure error
Remote procedure error
System clock time at alert sender set incorrectly
Unauthorized access attempted
Unauthorized access attempted on &1
Resource &1 not started in remote node
&1 not started
System resource &1 locked
&1 reached account limitation
Network control block (NCB) resource shortage on &1
Operator deleted &1
Operator deleted &1 in adjacent node
Operator requested alternate route for APPN high performance routing traffic to &1
&1 exceeded storage limit on &2
Dump requested
Microcode dump requested
Software dump requested
File full
Diskette or directory full
File full:
File needs reorganization:
File directory table full on &1
File almost full &1
Dirty read/write head
Blocked air filter
Software license management
License usage threshold exceeded for
License usage limit reached for
License usage limit exceeded for
License usage limit increase may violate contract for
Invalid transit network routing selected
Channel request invalid
There are no deleted files using storage space
User account added
User password changed
Configuration updated via network
Configuration updated via diskette
Configuration updated via operator interface
Error may be in UTC offset or daylight savings time settings
Insufficient storage media space available for &1
&1 kilobytes of storage is in use by deleted files that cannot be purged yet
Problem detected by &1
Failing component is identified by
Request originated from &1 on &2
Problem is related to the controller located at
Failing component is identified by &1 &2 &3
Failing component is identified by &4
Abend code
Adapter check status
Adapter return code
BOP code
Protocol code
Command code
Error code
Operating system return code
Event code
LLC error code
Machine check code
Malfunction code
Program check code
Reason code
Return code
Sense code
Sense data
Software error code
Status code
Symptom code
SNA sense data
Bus status code
Ring status code
Call progress signal
X.25 clear packet, cause code
X.25 reset packet, cause code
X.25 restart packet, cause code
X.25 diagnostic code
Diagnostic explanation
Database return code
Message code
Panel error message code
System message code
Message severity
Wait state code
Primary return code
Secondary return code
Socket number
V.25BIS indication
ICA sense code
Maintenance indicator
Access unit id
Controlled access unit lobe number
D-channel number
Reference code
System reference code
Replaceable unit code
Component id
Communication control unit
Part number
Card slot
Cable position
Interconnect controller
Error recovery procedure
PDP code
Backup path status
Wrap status
Attachment module status
Configuration data
Lobes deactivated
Attachment module number
Number of links lost
Number of NETBIOS sessions lost
Location name
Class of service
Back-up d-channel number
Route affected
Active route
Channel unit address
Device address
Line address
Line address range
Adapter at address
DTE address called
DTE address calling
Local DTE address
Card number
Card name
Card location
LAN bridge id
Token-ring id
Port number
Adapter number
Channel adapter number
Line adapter number
Line interface coupler (LIC) position
Bus number
Token ring interface coupler number
Locally-initiated logical channel
Remotely-initiated logical channel
Controller id
Device id
Transmission priority field
Program status word
Domain controller
Peer server
Generation parameter
Threshold parameter
Configuration object/record
Configuration parameter
IPL parameter
Parameter value
Security database file
Account system file
Substitute part number
Central processor complex
Central processing unit
Logical partition name
Subchannel number
Channel path id
I/O processing element id
Link station
Transaction program
Relational database
Fully qualified PCID
Logical partitions
Vector processor
Julian date
File server
Data stream
Data stream offset
Service processor
Expanded storage
Central processor complex image
Service update
Customer problem report
Byte offset
Bit offset
Detecting module
Failing module
Maintenance level
Maximum number of node table entries
Mode name
Unbind type
Inbound call
System error
Remote support facility
Central operations
Control program
EIA standard
CCITT standard
Channel subsystem
Message log
Operating system log
Retry count
Timer setting
Line speed (bits per second)
Line speed (kilobits per second)
Line speed (megabits per second)
Operation number
Operation priority
Operation input arrival time
SNA sense data received in XID
Application input arrival time
Alarm signal
Job number
ISDN cause code
Controller description object
Communication line description object
Logical device description object
Network interface description object
Network interface name
Job name
Line name
Message file name
Message queue name
Message reference key
Remote location name
File name
Log record number
Air filter number
Telephone number
Calling telephone number

Length: 253859 Date: 20230206 Time: 224523

Count: 1401     sap01-206 ( 1440 ms ) This documentation is copyright by IBM.