|
|
This chapter describes the messages issued by the Infrastructure (IFS) program. These include messages T00IF001 through T00IF999.
Explanation An IFS-type address space has been started by an MVS operator command.
Explanation Basic address space initialization is complete. Initialization includes establishing a long-term enqueue to prevent a second copy of this address space from starting, identifying PC call tables to MVS, identifying an extended ECB exit to MVS, and initializing the job step task.
Explanation During initialization of the address space, the long-term enqueue has failed. This means that another address space with the same definition type must already be active.
Recommended Action Terminate the existing address space, or direct commands to the existing address space if it performs the desired functions.
Explanation A task, in response to a START command, has completed initialization.
Explanation A task, in response to a STOP command, has terminated. The parameter tg_name indicates the task group name.
Explanation An error occurred during task initialization.
| uniq | Unique name of the address space where the failure occurred. |
| prfx | Prefix name of the address space where the failure occurred. |
| itgb | String ITGB, indicating IFS Task Group Block. |
| tgid | Task group identifier. |
| tg_name | Task group name. |
Recommended Action Call Customer Support.
Explanation A task group error occurred while holding the MVS local lock. A Functional Recovery Routine has gained control.
| uniq | Unique name of the address space where the failure occurred. |
| prfx | Prefix name of the address space where the failure occurred. |
| itgb | String ITGB, indicating IFS Task Group Block. |
| tg_id | Task group identifier. |
| tg_name | Task group name. |
Recommended Action Call Customer Support.
Explanation A task group error occurred during MVS wait. A Functional Recovery Routine has gained control.
| uniq | Unique name of the address space where the failure occurred. |
| prfx | Prefix name of the address space where the failure occurred. |
| itgb | String ITGB, indicating IFS Task Group Block. |
| tg_id | Task group identifier. |
| tg_name | Task group name. |
Recommended Action Call Customer Support.
Explanation A task group error occurred during local dispatching. A Functional Recovery Routine has gained control.
| uniq | Unique name of the address space where the failure occurred. |
| prfx | Prefix name of the address space where the failure occurred. |
| itgb | String ITGB, indicating IFS Task Group Block. |
| tg_id | Task group identifier. |
| tg_name | Task group name. |
Recommended Action Call Customer Support.
Explanation A task group error occurred after MVS post. A Functional Recovery Routine has gained control.
| uniq | Unique name of the address space where the failure occurred. |
| prfx | Prefix name of the address space where the failure occurred. |
| itgb | String ITGB, indicating IFS Task Group Block. |
| tg_id | Task group identifier. |
| tg_name | Task group name. |
Recommended Action Call Customer Support.
Explanation A task group error occurred during local dispatching. A Functional Recovery Routine has gained control.
| uniq | Unique name of the address space where the failure occurred. |
| prfx | Prefix name of the address space where the failure occurred. |
| itgb | String ITGB, indicating IFS Task Group Block. |
| tg_id | Task group identifier. |
| tg_name | Task group name. |
Recommended Action Call Customer Support.
Explanation A task group error occurred during resume dispatching. A Functional Recovery Routine has gained control.
| uniq | Unique name of the address space where the failure occurred. |
| prfx | Prefix name of the address space where the failure occurred. |
| itgb | String ITGB, indicating IFS Task Group Block. |
| tg_id | Task group identifier. |
| tg_name | Task group name. |
Recommended Action Call Customer Support.
Explanation TSO parse service routines failed while parsing an operator command. This occurs when the command syntax has been confused or is incorrect. Special characters can also cause parse failures.
Another condition which can generate this error occurs when the Subsystem Recognition Character (SRC) is set to the same as that used by JES (JES2 uses $, JES3 uses *).
The variable ret_code is a decimal return code from the TSO Parse Service routine. The return code is one of the following:
Recommended Action Try to reenter a correct command or eliminate special characters.
If your SRC is either $ or *, check with your JES Systems Programmer about what character you can use.
Explanation An invalid command verb was directed to the task group. The command was directed to the task group explicitly.
Recommended Action Try to reenter a correct command verb, direct it to another task, or omit the task group from the command.
Explanation A START or STOP command was issued, but the required task group type was not supplied with the command.
Recommended Action Reissue the command, specifying a three-character task group name with the start command.
Explanation A START, STOP, SET, or TASK command was issued, but the requested task group type is invalid or the component is not installed. The variable tg_id identifies the task group.
Recommended Action Specify a valid three-character task group name and reissue the command.
Explanation A START command was issued, but the requested task group already has the maximum number of active tasks permitted. The variable tg_id identifies the task group.
Recommended Action Usable subtasks for the requested task group should already be active. Display them with the TASK command. If no tasks exist and none can be started, stop and restart the address space where the problem occurred.
Explanation A STOP command was issued, but the requested task group type has no active subtasks. The variable tg_id identifies the task group.
Recommended Action Correct the command syntax and retry.
Explanation A START, STOP, SET or TASK command was issued, but the format of the requested task group specification is incorrect. The variable tg_id identifies the task group.
Recommended Action Specify a valid three-character task group name and reissue the command.
Explanation An operator requested, or ABEND initiated snap is complete. The variable cls_name, identifies the JES SYSOUT class to which the snap was dynamically allocated.
Recommended Action If the class is serviced by a JES printer, it is printed. If the class is not serviced by a JES printer, an external writer procedure must be initiated to collect the snap output.
Explanation A request for page-fix or page-free service failed.
Possible object types are the following:
Possible actions are the following:
The variable rsn_code is a decimal reason number for the failure; either 4 (module nonexistent) or 16 (A(object)=0).
Explanation Displays main storage. In the message text, the hexadecimal parameter stor_addr is the beginning address of the storage being displayed, and key is the storage key.
Explanation Displays a control block in main storage. The variable stor_addr is the beginning address, in hexadecimal, of the storage displayed.
Explanation Displays main storage. Shows sixteen bytes per line.
| addr | Virtual address. |
| disp | Displacement from the beginning address of the storage being displayed, in hexadecimal display form. |
| wrd1 | Contents of the first word in hexadecimal display form. |
| wrd2 | Contents of the second word in hexadecimal display form. |
| wrd3 | Contents of the third word in hexadecimal display form. |
| wrd4 | Contents of the fourth word in hexadecimal display form. |
| chars16 | Contents of the four words in character display form. |
Explanation Displays the component maintenance status in response to a status command.
Explanation This is a response to a $ROUTE command to either display or vary Route Codes for a task group. The variable rt_code is a string of route code numbers representing the current settings in effect for the task group.
Explanation This is a response to a $ROUTE command vary Route Codes for a task group. There is a value in the new route code specification outside the acceptable range of values of 1 to 16.
Recommended Action The request is ignored. Reenter the request, if desired, with a set of correct route code values.
This is a response to a $CON command to either display or vary Console Routing for a task group. The parameter cons_id is a hexadecimal word representing the current task console routing.
IF the first half of the word is... | THEN the... |
|---|---|
| nonzero | routing is to a TSO terminal. |
| zero | second half word represents a one byte console ID and a one byte area ID for that console. |
area_id corresponds to the WTO AREAID option and forces WTO descriptor codes to 8 and 9.
Explanation This is an error message from the Component Authorization facility. The key entered in the AUTH statement of the IJTCFG00 member is not the correct length. This message will also appear on the console log.
Recommended Action Examine the IJTCFG00 member of the PARM data set. Edit the KEY field with the correct key from the Component Authorization form. Stop and restart Cisco IOS for S/390 for the new key to take effect. If the message is repeated, contact Customer Support.
Explanation This message reports an error detected by the Component Authorization facility. This message will also appear on the console log.
Recommended Action
Explanation An error was detected by the Component Authorization facility. You may not run the Cisco IOS for S/390 product on this CPU. This message will also appear on the console log.
Recommended Action Verify your CPU ID and contact Customer Support.
Explanation An error was detected by the Component Authorization facility parsing the AUTH statement of the IJTCFG00 member. This message will also appear on the console log.
Recommended Action Examine the IJTCFG00 member of the PARM data set. Verify that the AUTH statement has the correct number of parentheses and that the key and customer number were entered correctly.
Explanation The Component Authorization facility has determined that an attempt has been made to start TCP/IP past the expiration date encoded in the authorization key. This message will also appear on the console log.
Recommended Action Contact Customer Support for a new authorization key.
Explanation IILATCH call for function function_name for latch latch_name failed with a return code of ret_code. The latch address is at location latch_addr.
Recommended Action This problem should not occur during normal operation. Look for related messages in the logs. Dump the address space via the operator console and contact Customer Support.
Issue the "/f jobname,ilatch free" command to free any held latches.
Explanation TCP was unable to allocate a timer element for a new connection. Either there are the maximum number of connections active or there was no virtual storage for the timer element.
Recommended Action Increase the virtual storage available to the address space or retry the connection when there are fewer other connections.
Explanation An error was detected by the Component Authorization facility parsing the IJTCFG00 member. The AUTH statement is required for component authorization. This message will also appear on the console log.
Recommended Action Edit the IJTCFG00 member of the PARM data set to include the AUTH statement, including the CUSTNUM and KEY fields. Contact Customer Support if you don't know your customer number or key.
Explanation The Component Authorization facility has determined that the expiration date for one or more of the features of Cisco IOS for S/390 will arrive in nnnn days. This message will also appear on the console log.
Recommended Action Contact Customer Support for a new component authorization key.
Explanation A latch has been found that has been held for too long. number is the number of seconds used to determine if the latch has been held too long.
Recommended Action Use the ILATCH DISPLAY command to determine who is holding the latch. Consider terminating that user; consider using the ILATCH FREE command to release the latch.
Explanation A latch is being freed by the ILATCH command processor. Subsequent messages will display information about the latch being freed.
Explanation The ILATCH command processor was unable to free a latch as requested. ret_code is the return code from the ILATCH FREE call.
Recommended Action Contact Customer Support and tell them the return code from the message.
Explanation This is the end of processing a ILATCH command.
Explanation The ILATCH command processor was unable to locate the Latch Work Area and is unable to process the command. The Latch Work Area should be allocated as part of initialization.
Recommended Action Contact Customer Support.
Explanation The ILATCH command processor was unable to locate the Level 1 Latch Map, and is unable to process the command. The Level 1 Latch Map should be allocated as part of initialization.
Recommended Action Contact Customer Support.
Explanation The ILATCH command processor was unable to locate the Level 2 Latch Map and is unable to process the command. The Level 2 Latch Map should be allocated as part of initialization.
Recommended Action Contact Customer Support.
Explanation A latch is being displayed. This message will be followed by messages T00IF046I and T00IF047I for exclusive latches, or T00IF057I and T00IF058I for shared latches.
Explanation Header information for message T00IF047I.
Explanation This message is the result of processing an ILATCH command that displays exclusive latches. The latch number specified in the command either was not currently held, or was held less than the specified (or default) time value.
Explanation Enter the ILATCH DISPLAY command to determine if the latch number is still held, or the amount of time it has been held. Then re-enter the ILATCH command as desired.
| latchnum | Latch number. |
| latchaddr | Latch block address. |
| addr_id | Address space ID of the holder of the latch. |
| ASCBaddr | Address of the ASCB of the holder of the latch. |
| TCBaddr | TCB address or the SRB address. |
| rbaddr | RB address or the first 8 bytes of the SRB token. |
| jobname | As displayed by SDSF DA command. |
| time | Number of seconds the latch has been held. |
Explanation The requested latch is not being held or has not been held as long as the TIME operand of the ILATCH command specifies.
Recommended Action Specify a different TIME keyword or a different latch number. Or it is possible the specified latch is no longer held.
Explanation The routine routine_name failed with the abend code specified.
Recommended Action Notify Customer Support.
Explanation A standard IFS recovery routine has gained control from a module ABEND situation and is displaying the ABEND situation.
| sabnd | MVS system ABEND code (hexadecimal). |
| uabnd | Application user ABEND code (decimal). |
| mod_id | Module identification, including CSECT name, assembly time and date, and version and level of the module. |
| mod_size | Size of the module in bytes (hexadecimal). |
Recommended Action Notify Customer Support.
Explanation The PSW, interrupt code, failing instruction, and displacement of the failure in a module (if possible) are formatted. See message T00IF050E.
| psw1 | First word, in hexadecimal, of the Program Status Word at time of failure |
| psw2 | Second word of the Program Status Word at time of failure. This word contains the address of the failing instruction (hexadecimal). |
| icde | Hexadecimal interrupt code causing the failure |
| idata | Failing instruction (hexadecimal) |
| disp | Displacement of the failing instruction in the ABENDing module, in hexadecimal |
Recommended Action Notify Customer Support.
Explanation This message contains information formatted for the task group associated with the ABEND. See message T00IF050E.
| tg_id | Task group ID. |
| tg_name | Task group name. |
| itgb | Hexadecimal address of the failing IFS Task Group Block. |
| itcb | Hexadecimal address of the failing IFS Task Control Block. |
| flg1 | Hexadecimal value of flag1 in the IFS Task Control Block. |
| flg2 | Hexadecimal value of flag2 in the IFS Task Control Block. |
| tcb | Hexadecimal address of the failing MVS Task Control Block. |
| csrb | Hexadecimal address of the associated IFS Command SRB. |
Recommended Action Notify Customer Support.
Explanation This message contains formatted register information associated with the ABEND. This line appears four times, each time with four of the sixteen hexadecimal registers. See message T00IF050E.
| r1 | First register shown on the line, either 0, 4, 8, or C. |
| r2 | Last register shown on the line, either 3, 7, 9, or F. |
| reg1 | Value of the first register in the group, 0, 4, 8, or 12. |
| reg2 | Value of the second register in the group, 1, 5, 9, or 13. |
| reg3 | Value of the third register in the group, 2, 6, 10, or 14. |
| reg4 | Value of the fourth register in the group, 3, 7, 11, or 15. |
Recommended Action Notify Customer Support.
Explanation This message contains formatted information from the MVS System Diagnostic Work Area associated with the ABEND. See message T00IF050E.
| erra | Hexadecimal value of the byte known as SDWAERRA. |
| errb | Hexadecimal value of the byte known as SDWAERRB. |
| errc | Hexadecimal value of the byte known as SDWAERRC. |
| errd | Hexadecimal value of the byte known as SDWAERRD. |
Recommended Action Notify Customer Support.
Explanation This message is in response to a VTAM command, showing the address of the VTAM Communication Vector Table built. The single parameter, vcvt, is the hexadecimal address of the VTAM CVT.
Explanation This message is in response to a VTAM command, showing the address of the VTAM Communication Vector Table that has already been installed by a previous VTAM command. The single parameter, vcvt, is the address of the VTAM CVT.
Explanation Header information for message T00IF058I.
Explanation This message is the result of processing an ILATCH command that displays shared latches. The latch number specified in the command either was not currently held, or was held less than the specified (or default) time value.
Explanation Enter the ILATCH DISPLAY command to determine if the latch number is still held, or the amount of time it has been held. Then re-enter the ILATCH command as desired.
| latch_num | Latch number. |
| latch_addr | Latch block address. |
| Shr_cnt | Shared count. |
| time_held | Number of seconds the latch has been held. |
Explanation If the Fault Tolerance option is not installed, the startup sequence will fail with this message if either the IP statement contains the GATED keyword, or if the MEDIA statement contains the IDLENET keyword.
Explanation There was a syntax error on the ABEND command. The allowable values are S0C1-S0CF, and S806.
Recommended Action Correct the syntax and retry.
Explanation A date stamp of the start of the log file.
Explanation Messages T00IF063E, T00IF064E, and T00IF065E always display together.
An incompatibly was recognized between a system startup stage and residual components from the previous running system. The residual components are still resident because the previous termination did not specify a P,CLEAR option.
Recommended Action Reactivate the previous version of TCP/IP, terminate it with the CLEAR option, then restart the newer version.
Explanation This message displays an estimate of the used and available virtual storage, first for the below-the-line area, then for above-the-line. The numbers are extracted from the VSMLIST statistics as reported by MVS. The available byte values are based on subtraction from the region size.
Explanation Message display and frequency is governed by the VSREPORT keyword of the IFSPARM statement in the IJTCFGxx member. Statistics are recalculated with each display to insure accuracy.
| vvv | Current amount of unallocated virtual storage, in bytes. |
| above/below | Either ABOVE or BELOW the 16MB line. |
| uu | Current amount used, expressed as a percentage of the region size. |
| mm | Minimum amount used, expressed as a percentage of the region size. |
| xx | Maximum amount used, expressed as a percentage of the region size. |
Explanation Both region sizes are displayed for the Cisco IOS for S/390 job as byte counts.
The region size specifies the maximum amount of storage that can be allocated to the Cisco IOS for S/390 job by any single variable-length GETMAIN request. Depending on how the region size was requested, it may include the region above 16MB. The below-the-line value specifies the maximum total storage that can be allocated to below-the-line requests.
Explanation These values are set by the IBM-supplied or installation-written exit routine. The region size usually is set equal to the REGION parameter specified by the Cisco IOS for S/390 JCL (or installation default if not specified), and the region size limit is usually equal to the region size plus 64K.
| value1 | The region size registered. |
| value2 | The size of the region below the 16MB line. |
Explanation This message displays during a message logging procedure when a date change is detected. It identifies subsequent log entries with their appropriate logging date.
Explanation The security handling module is invoked.
Explanation This is an Internal error. The TCP/IP system will abend.
Recommended Action Call Customer Support
Explanation This message displays when a userid attempts to log on.
Explanation This message displays when a userid logs off.
Explanation This message displays when a data set name is authorized.
Explanation This message displays when the ACEE monitoring option is selected.
Explanation This message displays when the ACEE monitoring option is selected.
Explanation This message displays at startup when the private security directory is built.
Explanation This message displays at termination when the private security directory is deleted.
Explanation This message displays when authorization for a userid is verified.
Explanation This message displays the return and feedback codes from the authorization subsystem interface.
Explanation This message usually follows another message and displays the userid and termid.
Explanation This message usually follows another message and displays the resource (such as a data set name).
Explanation This is associated with ACEE monitoring and displays the SECACEE address.
Explanation This is associated with ACEE monitoring and displays the TCBACEE address.
Explanation This is associated with ACEE monitoring and displays the TCB address.
Explanation This message displays when the password for a userid is verified.
Explanation This message is a confirmation that the timer support initialization and allocation routines have successfully completed.
Explanation The timer initialization routines failed due to storage or system related reasons.
Recommended Action Notify Customer Support.
Explanation The timer allocation routines failed due to storage or system related reasons.
Recommended Action Notify Customer Support.
Explanation Storage utilization is above the alarm percentage specified in the MAXSTGPCT keyword of the IFSPARM statement in the IJTCFGxx member. Message T00IF093I will report storage utilization dropping back to acceptable levels.
Recommended Action If the utilization drops below the threshold percentage, an occasional spike may be acceptable. If the system is constantly at this high level, a larger region allocation may be appropriate.
Explanation Storage utilization has dropped below the warning threshold. This message should shortly follow T00IF092W. If it does not, refer to the recommended action procedures following message T00IF092W.
Explanation The system BLDL function failed with return code ret_code. The module table is identified by name.
Recommended Action One of the most common failures is missing libraries; make sure the Loadlib concatenation is correct. Otherwise, examine the return code in the IBM documentation of the BLDL support.
Explanation The system load mechanism failed for module name.
Recommended Action Make sure the module is cataloged somewhere in the Loadlib chain.
Explanation An attempt to write a record to the SMF data set failed. A ret_code of 12 indicates that the SMFEWTM macro failed. The SMFEWTM return code is given in rsn_code. The SMF record subtype is sub_type. If multiple sequential failures occur, Cisco IOS for S/390 will suppress all but the first message to avoid flooding the console or message logs. When a record is successfully written to the SMF data set, the internal indicator is reset and another message will be written if there is a subsequent failure.
Recommended Action If ret_code is 12, see the IBM MVS System Management (SMF) manual for an explanation of the SMFEWTM return codes and respond appropriately. If ret_code value is other than 12, an internal error has occurred. Call Customer Support.
Explanation The display from the ILATCH TRACE function is complete.
Explanation Insufficient storage to satisfy the ILATCH tracing request.
Recommended Action If this is a transient condition, retry the tracing request.
Explanation ILATCH tracing was requested earlier and is still active.
Recommended Action None required.
Explanation ILATCH trace termination did not find active ILATCH tracing.
Recommended Action None required.
Explanation ILATCH tracing is requested too early in the startup sequence.
Recommended Action Wait until more of the system is active and retry.
Explanation The number of entries must be at least 1.
Recommended Action Correct the ENTRIES keyword and retry.
Explanation num_lost entries were lost due to a small table num_secs seconds ago.
Recommended Action Increase the ENTRIES value and reactivate the ILATCH trace.
Explanation Header line for message T00IF113I
Explanation Data display for the ILATCH TRACE command.
| aaaaaaaa | Name of module issuing the ILATCH request. |
| bbbb | Hex offset into module aaaaaaaa. |
| cccccccc | Address of the requested ILATCH block. |
| ddddd | Number of the requested ILATCH. |
| eeeee | Time latch held (in seconds). |
| ff | Return code from latch request call. |
| gggg | Either "Excl" or "Shrd" to identify the type. |
| hhhhh | Current use counter. |
Explanation The operator command LOGGING was successfully executed.
Explanation The operator command LOGGING encountered parsing errors. A previous message will identify the actual error.
Recommended Action Correct the syntax error and retry the LOGGING command.
Explanation Header information for message T00IF117I. This is output from the ILATCH CONTENTION command.
Explanation This message displays latches suspended due to contention.
Explanation A dump request was made by Cisco IOS for S/390 but the dump was suppressed by Dump Analysis and Elimination (DAE). For more information about DAE, see the IBM manual OS/390 MVS Diagnosis: Tools and Service Aids.
Explanation A dump request was made by Cisco IOS for S/390 but failed because no dump data sets were available.
Recommended Action Clear any unneeded dump data sets.
Explanation A dump request was made by Cisco IOS for S/390 but failed with return code ret_code.
Recommended Action See the IBM manual S/30 MVS Auth Assembler Services Reference, Vol. 3 (LLA-SDU) for a description of the SDUMPX return codes. Take any appropriate action. If the return code indicates an error on the part of the caller of SDUMPX, contact Customer Support.
Explanation This message follows message T00IF118I, T00IF119W, or T00IF120W, and provides the title of the dump referred to in the previous message.
Explanation More than a maximum number of messages were queued for processing. This happens when a large number of requests for a message are generated. An internal counter for the message number has been exceeded and the system is trying to avoid using up large amounts of storage for the message requests.
| num_suppressed | Number of messages suppressed. |
| msg_num | Message number of the messages that were suppressed. |
Explanation In this release, the startup JCL for TCP, IUCV, and Trace contains a keyword PRFX=. The value for TCP is T01, the value for IUCV is T02, and the value for Trace is T03. Each also contains a keyword UN=. This keyword must have a unique value for TCP, IUCV, and Trace.
This message indicates that a subsystem (UN=) was used for one PRFX= value, then re-used for another PRFX= value without an intervening /P CLEAR or re-IPL.
Recommended Action Restart the address space using the previous PRFX= value and issue a /P CLEAR or re-IPL the system, or change the UN= value for this address space.
Explanation See message T00IF123E, which also should have been issued. xxx is the PRFX= value that was used previously.
Recommended Action Restart the address space using the previous PRFX= value and issue a /P CLEAR or re-IPL the system, or change the UN= value for this address space.
Explanation A standardized message from the tables was requested, but no prototype was found.
| msg_num | Message number requested from the message tables. |
| tg_name | Name of the task group requesting the message. |
Recommended Action The message request is bypassed. Processing continues. Notify development support personnel.
Explanation A prototype message from the tables was found to have format errors. The most likely cause is ampersands not coded in pairs, or the character after a pair of ampersands not being recognized as an editing letter-type designator.
| msg_num | Message number requested from the message tables. |
| tg_name | Name of the task group requesting the message. |
Recommended Action The message request is bypassed. Processing continues. Notify your development system support group or Customer Support.
Explanation An ABEND occurred while issuing a message for the user. The most likely cause is bad addresses being requested for display. abend is a hexadecimal ABEND code associated with the failure.
| abend | Hexadecimal ABEND code associated with the failure. |
| msg_num | Message number requested from the message tables. |
| tg_name | Name of the task group requesting the message. |
Recommended Action The message request is bypassed. Processing continues with recovery attempted. Notify your development system support group or Customer Support.
Explanation The IMSG formatting routines encountered a message prefix with an invalid component identifier in positions 4-5.
Recommended Action This is an internal problem. Call Customer Support.
Explanation A general message for terminating multi-line WTO sequences.
|
|