Networking and Data Communications Library SNAX/HLS Diagnosis and Support Manual Abstract SNAX/HLS provides a general, high-level interface for application programs to communicate with intelligent SNA devices and software products. This manual provides information on maintaining SNAX/HLS. Part Number 104706 Edition Second Published November 1994 Product Version SNAX/HLS D30 Release ID Supported Releases D30 This manual supports D30.
Document History Edition Part Number Product Version Earliest Supported Release Published First Update 1 Second 064392 068533 104706 SNAX/HLS C20 SNAX/HLS D10 SNAX/HLS D30 C30.06 D10 D30 December 1991 February 1993 November 1994 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .
New and Changed Information This new edition of the SNAX/HLS Diagnosis and Support Manual (part number 104706) replaces the previous edition (part number 064392). All changes are noted with change bars. The changes are as follows: Guardian 90 is now the Tandem NonStop Kernel. Appendix A, “Return and Error Codes,” has a new cause for return code 02, RCINVALID VERB.
New and Changed Information (This page left intentionally blank) iv 104706 Tandem Computers Incorporated
Contents About This Manual ix Notation Conventions Section 1 xiii Problem Determination Building an Operation History The Log File 1-1 The Trace File 1-1 1-1 Common Problems and Their Causes 1-2 Session Termination Due to Negative Responses 1-2 Session Terminated Due to Tandem SNA Access Method Errors Translation Mismatches 1-2 Documentation Needed to Resolve SNAX/HLS Problems General Documentation 1-2 Device-Specific Documentation 1-3 Gateway-Problem Documentation 1-3 Section 2 1-2 1-2 Using the
Contents SELECT Command 2-27 SYSTEM Command 2-28 VERSION Command 2-29 VOLUME Command 2-30 Trace Analysis Interpretation Appendix A Return and Error Codes Error Codes A-1 SNAX/HLS Return Codes Appendix B Appendix C 2-31 A-4 Error Messages Common Error Messages B-1 HLSTAP Error Messages B-5 SNAX/HLS Log Messages The First Level 1 Heading in Appendix A Appendix D SNAX/HLS Process Messages C-1 SNAX/HLS Session Messages C-16 C-1 Conversion of RDT Files Appendix E D-Series Operating System C
Contents Tables Table 2-1. Table D-1.
Contents (This page left intentionally blank) viii 104706 Tandem Computers Incorporated
About This Manual The purpose of SNAX/HLS (High-Level Support) is to allow Tandem application programs to communicate with SNA devices and host software. The purpose of this manual is to provide SNAX/HLS support information to those responsible for maintaining SNAX/HLS.
About This Manual Related IBM Documents Related IBM The following list identifies some of the more important IBM SNA manuals. These are Documents useful in planning and programming SNAX/HLS applications. Systems Network Architecture Concepts and Products (IBM Order No. GC30-3072) presents an overview of an SNA network and is suggested reading for a first exposure to SNA. Systems Network Architecture Technical Overview (IBM Order No.
About This Manual Related IBM Documents Your Comments Invited After you have had a chance to use this manual, please take a moment to fill out the Reader Comment Card and send it to us. The Reader Comment Card is located at the back of the printed manual and as a separate file in the CD Read Document List. You can fax the card to us at (408) 285-6660 or mail the card by using the business reply address on the back of the card in the printed manual.
About This Manual Related IBM Documents (This page left intentionally blank) xii 104706 Tandem Computers Incorporated
Notation Conventions The following list summarizes the conventions for syntax presentation in this manual. Notation Meaning UPPERCASE LETTERS Uppercase letters represent keywords and reserved words; enter these items exactly as shown. Lowercase italic letters represent variable items that you supply. Brackets enclose optional syntax items. A group of vertically aligned items enclosed in brackets represents a list of selections from which you can choose one, several, or none.
Notation Conventions (This page left intentionally blank) xiv 104706 Tandem Computers Incorporated
1 Problem Determination This section suggests ways to handle problems that can occur in a SNAX/HLS environment. Use the following steps to help you become efficient at troubleshooting SNAX/HLS. (You may also need this information if you have to escalate a problem to Tandem support personnel.) 1. Use the VPROC utility to get the SNAX/HLS version information. Use the HLSCOM PEEK command to obtain additional version information.
Problem Determination Common Problems and Their Causes Common Problems The following paragraphs suggest what to do to correct specific problems. and Their Causes Session Termination Due to Negative Responses If sessions are terminated because of negative responses, there is probably a BIND problem. Carefully review the BIND request and the negative response to discover the SNA protocol violation. If the violation is by the SNAX/HLS server, contact your Tandem system analyst.
Problem Determination Common Problems and Their Causes The SAVEABEND file (where applicable), if a save file was created by SNAX/HLS. The source-code listing, compilation listing, and binder listing of your installation’s customization routines (see the SNAX/HLS Application Programming Manual), together with the source listing for your installation’s SNAX/HLS application program.
Problem Determination Common Problems and Their Causes (This page left intentionally blank) 1–4 104706 Tandem Computers Incorporated
2 Using SNAX/HLS Trace Analysis Program Basic Components The SNAX/HLS Trace Analysis Program (HLSTAP) is a tool for SNAX/HLS system programmers and operators to use in problem determination. HLSTAP analyzes previously generated SNAX/HLS trace files and displays information (selected by the user) in a high-level, easy-to-understand format. Production of the trace files is under the control of the HLSCOM TRACE command (described in the SNAX/HLS Configuration and Control Manual).
Using SNAX/HLS Trace Analysis Program Basic Components The nature of the entity represented by the term line-name and lu-name depends on the Tandem SNA access method you use. For example, if you are using SNAX/XF as the access method, line-name refers to the SNAX/XF line and lu-name refers to the SNAX/XF LU on the SNAX/XF line. If you are using SNAX/CDF as the access method, line-name refers to the SNAX/CDF process name and lu-name refers to the SNAX/CDF OPENNAME of an APPL defined to the SNAX/CDF process.
Using SNAX/HLS Trace Analysis Program Running the HLSTAP Program Running the HLSTAP HLSTAP can be started using the command interpreter RUN command. HLSTAP Program runs in either interactive mode or noninteractive mode. In interactive mode, the HLSTAP IN file and OUT file are the same. By default, this file is your terminal. HLSTAP also supports IN and OUT process files. In noninteractive mode, the HLSTAP IN file and OUT file are different.
Using SNAX/HLS Trace Analysis Program Command Dictionary Command Dictionary Table 2-1 lists the HLSTAP commands. Details on using these commands are presented in the command dictionary that follows this table. Presented in alphabetic order for ease of reference, the command dictionary describes the individual HLSTAP commands. The entry for each command includes an introductory paragraph telling what the command does, an explanation of the command syntax, a list of considerations, and one or more examples.
Using SNAX/HLS Trace Analysis Program Command Dictionary ASSUME Command The ASSUME command sets the default line-name for expansion of LU-specifier parameters in DESELECT, INFO, and SELECT commands. ASSUME [ line-name ] line-name is a valid line-name. For more information on line-name, refer to “Basic Components” in this section. Considerations If the line-name parameter is omitted, the default line-name is cleared. Examples This command sets the default line-name to $SNA1.
Using SNAX/HLS Trace Analysis Program Command Dictionary CMDSYS Command The CMDSYS command sets the default system for expansion of all file names (except OBEY file names). CMDSYS [ \system-name ] \system-name is a system name. The initial setting is the default system used by the command interpreter when HLSTAP is started.
Using SNAX/HLS Trace Analysis Program Command Dictionary CMDVOL Command The CMDVOL command sets the default volume and subvolume names for the expansion of all file names (except OBEY file names). CMDVOL [ $volume-name [ .subvolume-name ] ] [ subvolume-name ] volume-name is a volume name. The initial setting is the default volume used by the command interpreter when HLSTAP was started. If volume-name is omitted, the previous setting is used. subvolume-name is a subvolume name.
Using SNAX/HLS Trace Analysis Program Command Dictionary CODESET Command This command is only relevant if the interchange code set (data written to and received from SNAX/XF or SNAX/CDF) is ASCII or EBCDIC, and not an extended form of EBCDIC that would require a mapping other than the standard ASCII-to-EBCDIC mapping to convert to Tandem internal format. The CODESET command directs HLSTAP to format text in user messages using either ASCII or EBCDIC character tables when translation is not in effect.
Using SNAX/HLS Trace Analysis Program Command Dictionary DESELECT Command The DESELECT command removes LUs from the current LU selection list. HLSTAP displays trace records only for LUs that have been selected for display by using the HLSTAP command SELECT. Both the SELECT and the DESELECT commands can reference a single LU, all LUs on a given line-name , or all LUs known to a single copy of SNAX/HLS. The DESELECT command is provided as a convenient command for refining the LU selection list.
Using SNAX/HLS Trace Analysis Program Command Dictionary ENV Command The ENV command displays the current trace environment. A variety of information is displayed, including the current command defaults, program versions, trace start and stop times, and the contents of the ETT (entity trace table). ENV Consideration An ENV command is automatically executed by HLSTAP whenever a FROM command is encountered. Example This command lists the current trace environment.
Using SNAX/HLS Trace Analysis Program Command Dictionary Assumed line Identifies the line-name specified in the last ASSUME command. Codeset default Specifies the current value of the code set selection. The following fields are displayed only if you have a trace file selected. Trace filename Specifies the name of the trace file currently selected for analysis. HLS process name Specifies the name of the SNAX/HLS process that recorded the trace.
Using SNAX/HLS Trace Analysis Program Command Dictionary Trace End Time 2–12 104706 Tandem Computers Incorporated Specifies the date and time when the trace for this LU was ended by using an HLSCOM TRACE DISABLE or a TRACE STOP command, or the session termination date and time if the INITIAL^TRACE configuration parameter was specified at SNAX/HLS startup.
Using SNAX/HLS Trace Analysis Program Command Dictionary EXIT Command The EXIT command is processed in one of two ways: 1. If HLSTAP is running interactively, the EXIT command stops the current HLSTAP. 2. If HLSTAP is running noninteractively, the EXIT command exits the current OBEY file and reduces the nesting level of OBEY-file execution. If the EXIT command reduces the level to zero, the HLSTAP process is terminated. See the OBEY command for more information on nesting levels.
Using SNAX/HLS Trace Analysis Program Command Dictionary FC Command The FC command provides the ability to edit or repeat a command line. The FC command can be used only in interactive mode. FC Consideration The FC command is used to fix the last interactive command.
Using SNAX/HLS Trace Analysis Program Command Dictionary FILES Command The FILES command displays the file names in a disk subvolume. FILES [ $volume-name [ .subvolume-name ] ] [ subvolume-name ] volume-name is the name of a disk volume. subvolume-name is the name of a disk subvolume. Consideration The FILES command is qualified by using the CMDVOL command defaults prior to expansion.
Using SNAX/HLS Trace Analysis Program Command Dictionary FROM Command The FROM command directs HLSTAP to open a trace file for analysis. If a trace file is currently open, HLSTAP closes the file prior to opening the new trace file. FROM file-name file-name is the name of a trace file produced from a SNAX/HLS trace that was started and stopped earlier. Considerations The file specified in this command is opened by using the call ALLOCATESEGMENT.
Using SNAX/HLS Trace Analysis Program Command Dictionary HELP Command The HELP command displays the syntax of HLSTAP commands. HELP [ topic ] topic specifies one of the following topics on which help is desired: command-name is the name of a HLSTAP command for which the syntax is to be displayed. is any parameter value that is enclosed in angle brackets (< >) when displayed by the command-name option. The angle brackets must be included.
Using SNAX/HLS Trace Analysis Program Command Dictionary INFO Command The INFO command displays for selected LUs the PROFILE information, the BIND information, and information related to session initialization. INFO LU-specifier LU-specifier is an LU specifier list in one of the basic forms. For more information, refer to the “Basic Components” subsection. Considerations All information displayed by using the INFO command is obtained from the trace ETT.
Using SNAX/HLS Trace Analysis Program Command Dictionary Figure 2-2. Example of INFO Command Display @info $sna2.#p0l001 Session HS Open Profile Appl Max Xlate LMO ID Name Plrty Mode Name Name Req Ind ------------------------------------------------------------1 $SNA2.
Using SNAX/HLS Trace Analysis Program Command Dictionary Profile Name This is the name of the PROFILE under which the session was established. Appl Name This is the PLU name carried in the BIND request. If the LU is type PLU, then the PLU name sent in the BIND is the name in the APPLICATION-NAME field of the OPEN-SESSION or HLS-OPEN verb. If this field is empty, then the PLU-NAME in the BIND record in the RDT table is used.
Using SNAX/HLS Trace Analysis Program Command Dictionary LOG Command The LOG command directs a copy of the input commands and output generated by HLSTAP to a file. LOG directive directive is one of the following: TO file-name specifies the name of the file to receive the copy of the commands and output. This form of the command initiates the logging function. STOP closes the log file and stops all logging.
Using SNAX/HLS Trace Analysis Program Command Dictionary NEXT Command The NEXT command displays consecutive records that match the SELECT criteria (if applicable), starting from the current position in the trace file. N[EXT] [ record-count ] record-count is the number of records to be displayed. The maximum is 32,767 records. Consideration If record-count is not specified, the default is 1.
Using SNAX/HLS Trace Analysis Program Command Dictionary OBEY Command The OBEY command causes commands to be read from a specified file. Such an OBEY file can itself contain OBEY command(s). The nesting of OBEY files can be up to three levels.
Using SNAX/HLS Trace Analysis Program Command Dictionary OBEYSYS Command The OBEYSYS command sets the default system for file-name expansion of files in OBEY commands. OBEYSYS [ \system-name ] \system-name is a Guardian system name. The initial setting is the system used by the command interpreter when HLSTAP was started. If system-name is omitted, OBEYSYS is cleared (there is no default), thus permitting reference to seven-character local device names that are too long to reference in network form.
Using SNAX/HLS Trace Analysis Program Command Dictionary OBEYVOL Command The OBEYVOL command sets the default volume and subvolume for expansion of OBEY file-names. OBEYVOL [ $volume-name [ .subvolume-name ] ] [ subvolume-name ] volume-name is a Guardian volume name. The initial setting is the default volume used by the command interpreter when HLSTAP was started. If $volume-name is omitted, the previous setting is used. subvolume-name is a Guardian subvolume name.
Using SNAX/HLS Trace Analysis Program Command Dictionary RECORD Command The RECORD command positions the current trace record and displays the record. RECORD argument argument is one of the following: record-number specifies a specific record to be displayed. start-rec,stop-rec specifies a range of records to be displayed. All records for selected LUs between start-rec and stop-rec are displayed (including start-rec and stop-rec).
Using SNAX/HLS Trace Analysis Program Command Dictionary SELECT Command The SELECT command adds LUs to the current LU selection list. HLSTAP displays trace records and INFO command output only for LUs that have been selected for display by using this command. SELECT LU-specifier LU-specifier is an LU-specifier in one of the basic forms. For more information, refer to the "Basic Components" subsection.
Using SNAX/HLS Trace Analysis Program Command Dictionary SYSTEM Command The SYSTEM command is used to set the default system for all file-name expansions. The SYSTEM command is equivalent to entering a CMDSYS command and an OBEYSYS command, both with the same system-name specification. SYSTEM [ \system-name ] \system-name is a Guardian system name. The initial setting is the default system name used by the command interpreter when HLSTAP was started.
Using SNAX/HLS Trace Analysis Program Command Dictionary VERSION Command The VERSION command causes HLSTAP to display its version banner.
Using SNAX/HLS Trace Analysis Program Command Dictionary VOLUME Command The VOLUME command sets the default volume and subvolume for expansion of all file names. The VOLUME command is equivalent to entering a CMDVOL command and an OBEYVOL command, both with the same volume and subvolume specifications. VOLUME [ $volume-name [ .subvolume-name ] ] [ subvolume-name ] volume-name is a Guardian volume name. The initial setting is the default volume used by the command interpreter when HLSTAP was started.
Using SNAX/HLS Trace Analysis Program Trace Analysis Interpretation Trace Analysis The HLSTAP utility formats traces configured by using HLSCOM commands. These Interpretation HLSCOM commands allow the specification of which trace data to accumulate on a session. The trace selections for one session are independent of the selections for another session. All sessions established can be traced automatically from their inception if you use the INITIAL^TRACE configuration parameter.
Using SNAX/HLS Trace Analysis Program Trace Analysis Interpretation Figure 2-3.
Appendix A Return and Error Codes SNAX/HLS returns error signals to the application in one of two ways: file-system error codes and SNAX/HLS return codes. These are explained below. Error Codes Code 2 When a file-system error code is returned to some operation your application has issued, you should consider the following three possible sources of the error: 1. The file system detected the error. (For more information, see the Systems Messages Manual for details.) 2. SNAX/HLS produced the error code.
Return and Error Codes Error Codes Code 21 Illegal Count Specified Cause. A verb was received in a WRITEREAD request with a read count less than 12. Effect. The verb request is not performed. Recovery. Correct the application so that it issues the request with the proper read count. Code 39 SYNC-ID Too old Cause. A sync ID was encountered that was older than the current sync ID minus the sync depth. Effect. The request is not performed. Recovery. The application may be performing checkpoints improperly.
Return and Error Codes Error Codes Code 187 Operation returning with no useful data Cause. An operation interrupted by CONTROL 26, 0 can complete with this code. Note that it is a WRITEREAD request that completes with this error, not the CONTROL request. Effect. The operation of the outstanding verb has been interrupted. Recovery. None. See the SNAX/HLS Application Programming Manual for a full description of when this code is returned. Code 189 Response not yet available Cause.
Return and Error Codes SNAX/HLS Return Codes SNAX/HLS Return The codes listed and defined in this subsection can be returned by SNAX/HLS in the Codes RETURN-CODE field of a verb reply. An application program should examine this field to determine how the implied operation completed. Each return-code value has a name assigned of the form: RC^xxx (in TAL) RC-xxx (in COBOL and SCOBOLX) The language text produced by the CONVERT-ERROR-CODE request can differ.
Return and Error Codes SNAX/HLS Return Codes 02 RC-INVALID-VERB Cause. The current request contains an invalid verb-code value. A standard reply format message is returned. VERB-CODE has been set to -1, SESSION-ID has been set to 0, and RETURN-CODE has been set to 2. All other indicators are not meaningful. The possible reasons for this response include: The verb code is out of range.
Return and Error Codes SNAX/HLS Return Codes 05 RC-SYNTAX-ERROR Cause. The verb request contains parameters in error. Effect. The verb request is rejected. Recovery. A verb reply is returned with this return code and the SYSTEM-ERROR-CODE field contains the ordinal number of the parameter in error, not counting the VERB-CODE, SESSION-ID fields, and the REQUEST-FORMAT and COMPLETION-MODE fields where they exist. Use this value to correct the application program. 06 RC-FILE-ERROR Cause.
Return and Error Codes SNAX/HLS Return Codes 08 RC-INVALID-COMPLETION-MODE Cause. The completion mode selected is not supported for the verb issued. Effect. The verb request is rejected. Recovery. Consult the SNAX/HLS Application Programming Manual for the verb in question. Correct the application program to select a supported completion mode. This error can occur only on verbs whose names begin with “HLS-.” 09 RC-MAX-REQUESTS-EXCEEDED Cause.
Return and Error Codes SNAX/HLS Return Codes 11 RC-VERIFY-FAILURE Cause. The OPEN-SESSION or HLS-OPEN request has indicated sequence number verification, and the session partners do not agree on the session sequence numbers. Effect. The session partner’s sequence numbers are returned in the verb reply. The session still exists when this return code is given to the application, although the session may soon be terminated.
Return and Error Codes SNAX/HLS Return Codes 13 RC-RESOURCE-IN-USE Cause. An attempt was made to allocate a LU that is already allocated and that does not use pipelining. Effect. The verb request is rejected. Recovery. If the situation should never arise based on application design, examine the application program for logic errors. If the problem is a contention problem, then retry the request later. 14 RC-FILE-NOT-SUITABLE Cause.
Return and Error Codes SNAX/HLS Return Codes 17 RC-SESSION-TERMINATED Cause. The session has been ended because of a request from the operator or the session partner (TERM-SELF or UNBIND) Effect. The SNA session is terminated. Recovery. Not applicable. 18 RC-DATA-TRUNCATED Cause. This indicates that the length of the message exceeds the space allotted by the verb reply. Effect. As much data as will fit in the verb reply is returned. The rest of the data is lost. Recovery. Not applicable.
Return and Error Codes SNAX/HLS Return Codes 21 RC-NOTIFICATION Cause. A previous SEND-DATA request (or a send portion of a SEND-AND-RECEIVE-DATA request) has been acknowledged by the session partner and the SEND-DATA request in question indicated notification. Effect. The program can infer that the session partner has accepted and understood the indicated request. The particular request is identified by the RECOVERY-TAGS values returned in the reply. Recovery. Not applicable.
Return and Error Codes SNAX/HLS Return Codes 24 RC-REQUEST-EXCEEDS-MAXRU Cause. The SEND-DATA or SEND-AND-RECEIVE-DATA verb contains user data whose length is in excess of the BIND-specified MAXRU. This return code is delivered only when the large message option (selected using the LMO PROFILE attribute) is being used in the session. Effect. No data has been transmitted to the session partner. Recovery.
Return and Error Codes SNAX/HLS Return Codes 27 RC-SESSION-NOT-ALLOCATED Cause. This indicates that a request was made involving a session that you do not have allocated. This may be due to the session partner terminating a session that you opened with the OPEN-SESSION (as opposed to the HLS-OPEN) verb or the session has been ended by SNAX/HLS because the session partner violated SNA protocol. Effect. The verb request is rejected. Recovery.
Return and Error Codes SNAX/HLS Return Codes (This page left intentionally blank) A–14 104706 Tandem Computers Incorporated
Appendix B Error Messages This appendix contains the error messages that are common to the HLSCOM, HLSRDT, and HLSTAP programs, as well as the error messages that are specific to the HLSTAP program. For information on specific error messages for the HLSCOM program refer to Appendix B of the SNAX/HLS Configuration and Control Manual. For information on specific error messages for the HLSRDT program refer to Appendix C of the SNAX/HLS Configuration and Control Manual.
Error Messages Common Error Messages Extraneous parameters on command Cause. Although you have specified a valid command, you have specified something beyond the defined end of the command. Effect. The command fails. Recovery. Check the syntax for the command and reissue the corrected command. Illegal syntax Cause. The command that you entered violated the syntax defined for that command. Effect. The command fails. Recovery. Check the command and syntax, then reissue the correct command.
Error Messages Common Error Messages Invalid file name Cause. You specified an invalid file name. Effect. The command fails. Recovery. Check the spelling of the file specification or check that the file exists, then reissue the correct command. Invalid line name Cause. You specified an invalid line name. Effect. The command fails. Recovery. Check the spelling of the line name or check that the line exists, then reissue the correct command. Invalid name Cause.
Error Messages HLSTAP Error Messages Invalid volume name Cause. You specified an invalid volume name. Effect. The command fails. Recovery. Check the spelling of the volume name or check that the volume exists, then reissue the correct command. OBEY file nesting limited to three levels Cause. You attempted to issue an OBEY command that is nested too deep. Effect. Processing for all nested OBEY files stops at the offending nested OBEY command. Recovery.
Error Messages HLSTAP Error Messages HLSTAP Error The following error messages are generated by the HLSTAP program. Messages End of trace file reached Cause. The HLSTAP program unexpectedly encountered the end of the trace file before reaching the requested record. Effect. The command fails. Recovery. This message can be considered an informational message. However, if you expected to see more records, check the command, especially the number that you entered, and reissue the corrected command.
Error Messages HLSTAP Error Messages No trace file currently open Cause. A command was issued that involved access to a trace file, but no trace file is currently open. Effect. The command fails. Recovery. Use the FROM command to open a trace file and reissue the correct command. The LUs specified were not found Cause. The LU names specified in the command could not be found among the set of LUs contained in the trace file. Effect. The command is ignored. Recovery.
Appendix C SNAX/HLS Log Messages This appendix lists common SNAX/HLS log messages. For information on messages that are not listed here, refer to the Communications Management Programming Manual. SNAX/HLS log file messages have the following format: ddmmmyy hh:mm:ss object name: message-text The log file messages are listed below, showing the object name and message-text portion. Valid SNAX/HLS objects are process name and session name.
SNAX/HLS Log Messages process name: Backup abended too many times Cause. Within the past 30 minutes (approximately) there were more than five successive attempts to initiate a backup process, all of which resulted in abnormal termination of the backup. Effect. No further attempts to start a backup process are made. Recovery. This might be either a hardware problem or a programming error in the subsystem.
SNAX/HLS Log Messages process name: Backup started in CPU n Cause. The backup process has been initiated in CPU n. Effect. None. Recovery. Informational message. No action necessary. process name: Backup process in CPU n stopped Cause. The backup process in the CPU specified in n terminated as expected. Effect. None. Recovery. Informational message. No action necessary. process name: Character map name not on file name Cause. The charactermap you specified is not on the charactermap file. Effect.
SNAX/HLS Log Messages process name: Continuation of EMS recording from file name of oldcollector Cause. An operator command switched the event collector function for the primary EMS collector to the collector at which this message appears. Effect. The event collection functions for the primary EMS collector have been switched from old-collector to another collector (usually identified by an EMS recording switched to message). Recovery. Informational message. No action necessary.
SNAX/HLS Log Messages process name: EMS recording has been switched to file name of new collector Cause. An operator command switched EMS recording for the primary EMS collector to another process. This is the last message on the old collector. Effect. The event collector function for the primary EMS collector has been switched to the new collector process. Recovery. Informational message. No action necessary. process name: EMS recording has been stopped Cause.
SNAX/HLS Log Messages process name: Failure allocating segment for role played by segment on name of segment file, size size of segment explanation Cause. An attempt to allocate an extended segment failed. The failure was due to reasons other than an I/O failure. See the Communications Management Programming Manual for a list of the possible values for explanation . Effect. The indicated segment has not been allocated. Recovery.
SNAX/HLS Log Messages process name: Insufficient memory to handle request from process process name Cause. There is insufficient memory available to handle a request from some other process. Effect. The request is rejected. Recovery. Storage overflow can occur for several reasons: Insufficient memory You might have initiated the process with a fixed amount of memory and it has proven insufficient. Examine the DATAPAGES configuration parameter and adjust as needed.
SNAX/HLS Log Messages process name: Log recording has been stopped Cause. An operator command terminated logging functions. Effect. Logging functions are terminated. Recovery. Informational message. No action necessary. process name: Log recording has been switched to name of new log file Cause. The log file has been switched to a new file. This message appears as the last message on the old log, provided it was accessible. Effect. None. Recovery. Informational message. No action necessary.
SNAX/HLS Log Messages process name: Message from unknown source, process: issuing process Cause. A message was detected that originated from a file that is not recorded as being open. This situation can occur after starting the subsystem when a previously running subsystem had the same name. Effect. The request is rejected. Recovery. Informational message. No action necessary. process name: Message with old sync ID, process: process issuing I/O, file number file number used by requester Cause.
SNAX/HLS Log Messages process name: Primary reopened with no backup close, process process issuing open, file number file number used by requester Cause. A primary process has re-opened a file that was already opened by the backup process (and before the backup closed the file). Effect. The OPEN command fails. Recovery. Examine how your application is handling CHECKCLOSE.
SNAX/HLS Log Messages process name: RDT must be a disk file, file = file-name Cause. The RDT file specified is not a disk file. Effect. The attempt to load the file is abandoned. If the load is the result of program initiation, the SNAX/HLS program is aborted. Recovery. Use a disk file. process name: reason Cause. The process terminated voluntarily, usually because of some operator action. Effect. The process is not running. There may have been a backup takeover. Recovery. Informational message.
SNAX/HLS Log Messages process name: Request from process issuing process name rejected because RECEIVE queue is full Cause. There are too many requests currently in progress in the subsystem. The actual number of requests that can be accommodated is specified by the RECEIVEDEPTH configuration parameter. For more information, refer to the SNAX/HLS Configuration and Control Manual. Effect. An application request is rejected with file system error 30 (no LCB space). Recovery.
SNAX/HLS Log Messages process name: SPI request from process issuing request bad: Invalid OCCURS value Cause. A SPI message was received with a byte count that cannot occur in a wellformed request message. It is possibly longer than the buffer transmitted, an odd number of bytes, or less than the smallest conceivable value for a valid request image. Effect. The request is rejected and the command fails. Recovery. Correct the byte count and reissue the corrected command.
SNAX/HLS Log Messages process name: Storage exhausted Cause. There is insufficient memory available to satisfy internal needs. Effect. The SNAX/HLS process process process name terminates. Recovery. Storage overflow can occur for several reasons: Insufficient memory—You might have initiated the process with a fixed amount of memory and it has proven insufficient. Examine the DATAPAGES startup argument and adjust as needed.
SNAX/HLS Log Messages process name: This product requires a NonStop processor and an XF release C00 or better Cause. The product was initiated on an inappropriate CPU. Effect. The process terminates. Recovery. Move the application to an appropriate processor. process name: Too many takeovers Cause.
SNAX/HLS Log Messages SNAX/HLS Session Messages session name: Attempt to send invalid MU, MU =message-unit [Sense Data = SNA sense data, explanation of SNA sense data] Cause. This situation can result from an invalid RDT data file. If an internal error in the HLSRDT program produces an invalid RDT, or if the operator swaps to an invalid RDT file, this message might result. Effect.
SNAX/HLS Log Messages session name: No memory for RU, RU will be discarded Cause. Memory congestion might result because the rate at which the messages are arriving exceeds the rate at which the messages are being processed by the program. Another reason for memory congestion is that the copy of SNAX/HLS is heavily loaded. Effect. The session is terminated. Recovery. You should check whether or not receive pacing is being used and, if not, whether or not you can introduce it.
SNAX/HLS Log Messages session name: (-RSP) received, MU =message-unit, explanation of SNA sense codes in RSP MU Cause. Typically, negative responses indicate either a mismatch of session-partner specifications (an incorrect profile specified to SNAX/HLS), protocol violations by the partner, or internal SNAX/HLS errors. There are two circumstances that are likely to cause this situation: The profile specified in a BIND or INIT-SELF record was incompatible with the device or gateway application.
SNAX/HLS Log Messages session name: SNAX buffer overload Cause. A temporary condition occurred in which SNAX/XF or SNAX/CDF had insufficient buffer space for the current processing requirements. Effect. Data is not lost. SNAX/HLS treats this condition automatically. The rejected send request is retried, and the rate at which data is sent to this LU is slowed down. When the overload errors cease, the submission rate is increased.
SNAX/HLS Log Messages (This page left intentionally blank) C–20 104706 Tandem Computers Incorporated
Appendix D Conversion of RDT Files The conversion program, HLSCRDT, is provided as a convenience tool to simplify the process of converting RDT environments (created prior to the C20 release) to text files suitable for submission to the HLSRDT program now in use.
Conversion of RDT Files The HLSCRDT program creates an EDIT format file that defines those objects defined by the old key-sequenced file. Once converted, the key-sequenced version should be archived, and all subsequent maintenance functions should be performed based upon this EDIT format file using conventional editors such as EDIT and TEDIT. The RUN command for HLSCRDT has the following syntax: RUN HLSCRDT / options / ; ks-filename text-filename /options/ are standard command interpreter options.
Appendix E Supplemental Information for D-Series Systems This appendix provides specific information about D-series SNAX/HLS relevant to the SNAX/HLS Diagnosis and Support Manual.
Supplemental Information for D-Series Systems (This E–2 page left intentionally blank) 104706 Tandem Computers Incorporated
Glossary This glossary defines terms used and referred to in SNA and SNAX/HLS. Several definitions have been borrowed from IBM’s Dictionary of Computing (SC20-1699) and IBM’s Network Program Products: General Information (GC30-3350). $SSCP. Process name of the SNAX/XF Service Manager. ANSI. American National Standards Institute. application prototyping and simulation. A SNAX/HLS tool used by software developers to quickly and easily determine how their applications work. APS.
Glossary communication interface unit (CIU ). A hardware unit that, together with the SNAXLink software and the CAU, provides a direct channel link between a Tandem system and an IBM system. The CIU controller attaches directly to the Tandem processor through a standard I/O card slot. Communications Management Interface (CMI). A Tandem subsystem that is used for configuring and controlling communications subsystems such as SNAX/XF. See also Subsystem Control Facility. configuration.
Glossary DTE. See data-terminal equipment. EIO. See execute I/O. EMS. See event management service. event. An event is an uncontrolled or unplanned transmission. Critical events are those conditions that applications cannot handle and that cause processes or even sessions to terminate. Noncritical events are conditions that applications can handle and from which they can recover. Action events are those events that require operator intervention. Event Management Service.
Glossary HLSTAP. Trace Analysis Program for SNAX/HLS. HLSTAP formats SNAX/HLS requests and responses in terms that do not require a detailed understanding of SNAX/HLS. HLSRDT. Constructs the resource definition table (RDT) for SNAX/HLS. The RDT is the configuration database for SNAX/HLS. Each RDT PROFILE contains the required SNA-specific information necessary to configure and initiate a session. This information includes such SNA parameters as the BIND and INIT–SELF. host.
Glossary microcode. A code representing the instructions of an instruction set that is implemented in a part of storage that is not program-addressable. MICROCODE_FILES paragraph. A paragraph within the SYSGEN configuration file that is used to indicate the location of the downloadable microcode for controllers and other devices. NAU. Network addressable unit. NCP. Network control program. network. A group of interconnected computer systems and devices, and the hardware and software used to connect them.
Glossary PERIPHERALS paragraph. A paragraph within the SYSGEN configuration file that is used to define the SNAX/XF $SSCP process (Service Manager) and the SNAX/XF lines. physical unit. That part of a device (hardware or software) that provides control functions for its own node and for the other less intelligent device nodes attached to the PU. pipelining. A session is pipelined if it can be accessed by more than one requester.
Glossary session. In SNA, a temporary logical connection between two NAUs for the purpose of exchanging data and control information in accordance with ground rules that have been agreed upon for that exchange. A session can be activated, tailored to provide various protocols, and deactivated, as requested. session passthrough. A SNAX/XF feature that allows the SNA host to control SNA devices on Tandem NonStop systems as if they were directly connected to the host. site update tape (SUT).
Glossary SSCP–SSCP session. In SNA, a session between the SSCP in one domain and the SSCP in another domain. An SSCP-SSCP session is used to initiate and terminate crossdomain LU-LU sessions. static passthrough. A passthrough mode that allows SLUs connected to a Tandem system to take the initiative in establishing sessions with host application programs. With static passthrough, the host SSCP can send USS messages to devices connected to a Tandem system. subsystem.
Glossary Systems Network Architecture Communications Services/Extended Facility (SNAX/XF). A Tandem software product that provides a gateway between Tandem NonStop systems and SNA systems and devices. With SNAX/XF, Tandem systems can function as fully integrated components of an SNA network. SNAX/XF allows SNA devices attached to a NonStop system either directly or through a switched line to use Tandem applications.
Glossary (This page left intentionally blank) Glossary–10 104706 Tandem Computers Incorporated
Index A Abnormal backup termination C-2 C Common error argument of our range B-1 extraneous parameters B-2 illegal syntax B-2 improper literal B-2 invalid device specifier B-2 invalid file name B-3 invalid line name B-3 invalid name B-3 invalid process name B-3 invalid system name B-3 invalid volume name B-4 missing delimiter B-1 numeric argument B-1 OBEY file nesting B-4 parameter missing B-4 unrecognized command B-4 unrecognized keyword B-4 Common error messages B-1 Compiled RDT tables D-1 Configuration e
Index F File-system error A-6 G Garbled messages,cause session termination 1-2 Gateway problems,documents for problem reporting 1-3 H HLS message active process C-10 allocation failure C-6 backup failure C-2 backup started C-3 backup stopped C-3 backup without primary open C-2, C-3 charactermap file not found C-3 customizer error C-4 dynamic memory available C-8 dynamic memory not available C-8 event collector switched C-4 event recording stopped C-4, C-5 event recording switched C-5 excessive takeovers C-
Index HLS message (continued) open rejected C-9 primary reopened backup before backup closed C-10 process stopped C-11 RDT file version mismatch C-10 RECEIVE queue overload C-12 RESETSYNC request C-12 SPI code word missing C-12 SPI header missing C-13 SPI request buffer error C-5 takeover by backup C-14 unexpected backup failure C-2 unnamed process C-10 unspecified local swap disk C-1 HLSCOM error messages B-1 HLSCRDT conversion program D-1 HLSRDT program D-1 HLSTAP 2-1, 2-31 command syntax 2-1 LU-specifie
Index HLSTAP commands (continued) VERSION 2-29 VOLUME 2-30 HLSTAP error incompatible trace file B-5 invalid ending record number B-5 invalid trace file name B-5 no open trace file B-6 specified LUs not found B-6 unexpected end of trace file B-5 HLSTAP error messages B-5 I Illegal Count A-2 Insufficient space A-8 Internal errors documentation 1-2 problem reporting 1-2 Invalid completion mode A-7 Invalid session ID A-5 Invalid verb length A-5 Invalid verb-code value A-5 K Key-sequenced file conversion D-1 Ke
Index N Negative responses,cause session termination 1-2 O OPEN request A-1, A-2 Operation history,building 1-1 OPRLOG file 1-1, 1-2 P PEEK file 1-2 Problem determination 1-1 Problem resolution,documentation needed 1-2 Problems and causes 1-2 PROFILE naming errors A-11 R RDT database D-2 RDT maintenance procedure D-1 RDTDATA D-2 RDTKSFLE file D-1, D-2 RECEIVE-CONTROL reply A-4 Request completion A-12 Request completion errors A-13 Request notification A-11 Request rejection A-11 Resource allocations A-6 Re
Index Session message (continued) negative response C-18 receive data overrun C-17 unexpected pacing response C-19 Session termination A-10 due to garbled messages 1-2 due to no communication 1-2 due to SNAX errors 1-2 Session termination,due to negative responses 1-2 SETMODE message A-1 SNAX errors,cause session termination 1-2 SNAX/HLS log messages C-1 SNAX/HLS,return codes A-4 State violations A-10 Swap disk C-1 sync ID A-2 Syntax errors A-6 T Tandem SNA access method SNAX/CDF 2-2 SNAX/XF 2-2 TCB availa
