The Developer Connection - Device Driver Kit for OS/2 3

home *** CD-ROM | disk | FTP | other *** search

/ The Developer Connection…ice Driver Kit for OS/2 3 / DEV3-D1.ISO / docs / pdguide.inf (.txt) < prev next >

Wrap

OS/2 Help File | 1993-08-15 | 293.0 KB | 10,789 lines

ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ The online Problem Determination Guide contains information to aid in problem determination for Communications Manager and for user-written programs that use the communications application programming interfaces (APIs). The information contained in this online document enables you to: o Identify problems or errors that might occur with Communications Manager o Gather information to resolve these problems or errors o Identify the tools available that can assist you in problem determination This online document contains the following sections: Problem Determination Procedures Which contains procedures that assist you in problem determination and resolution. This section also contains information to help you determine when it is appropriate to use the diagnostic tools provided by Communications Manager and when to contact your support personnel. First Failure Support Technology/2 (FFST/2) Which tells you how to use FFST/2 services for problem determination. FFST/2 services include: o Message log formatter o Message console o Dump formatter o System error log o FFST/2 command line interface Trace and Dump Services Which tells you how to use the Communications Manager Trace Services and the trace commands; CMTRACE and FMTTRACE. Examples of unformatted and formatted Communications Manager traces are also provided. These examples are useful for interpreting actual traces. Diagnostic Tools Which provides descriptions of additional diagnostic tools provided by Communications Manager. Sense Data Which contains descriptions of SNA-defined sense codes that may be generated during error processing. OS/2 Request Codes Which contains a list of OS/2 request codes that allows you to cross-reference these request codes with their associated function calls. ΓòÉΓòÉΓòÉ 2. Problem Determination Procedures ΓòÉΓòÉΓòÉ These procedures assist you in identifying and solving problems you may experience with Communications Manager by leading you through the diagnostic process in a logical manner. The purpose of these procedures is to enable experienced users, local support personnel, and IBM Service to follow a deductive process to identify the cause of a problem and correct the problem. In many cases, problems may be circumvented by restarting the workstation. If the problem persists following a restart, ask your local support personnel to help you through the procedures. ΓòÉΓòÉΓòÉ 2.1. How to Use These Procedures ΓòÉΓòÉΓòÉ The problem determination procedures are arranged so that you can perform the problem determination process in a logical, step-by-step manner. You can begin problem determination by selecting either "Fast Path Problem Determination" or "Procedures". Fast Path Problem Determination provides direct access to certain Communications Manager component procedures. Use Fast Path Problem Determination if you are experienced in using these procedures and you are sure that the problem originates in one of the Fast Path categories. Procedures provides full access to the Problem Determination Procedures. Selecting this choice displays a window that contains the following problem determination categories you can choose from: o Start Here o Problems Starting the Workstation o Hardware Diagnostics o Problems Starting Communications Manager o FFST/2 Diagnostics o Problems with Communications Manager Applications o Operational Problems Running Communications Manager o Problems Stopping Communications Manager o Following Through Generally, you should select "Start Here" to begin problem determination. However, you can select one of the other categories if you are sure that the origin of the problem falls under one of these categories. Throughout all of the procedures, windows appear that contain information about the problem. In many cases, the procedures prompt you to answer certain questions relating to the problem. You can answer the questions by selecting either the Yes or No push buttons that immediately follow the question. Depending on your answer, the procedure guides you to the appropriate information you need for problem determination. In some cases, a Continue push button is provided in the window. Selecting this push button also provides you with additional information. Selectable hypertext links that link you to other relevant sections or provide additional information are also provided throughout the procedures. ΓòÉΓòÉΓòÉ 2.2. Fast Path Problem Determination ΓòÉΓòÉΓòÉ Fast path problem determination provides direct access to certain Communications Manager component procedures. If you suspect the problem is associated with one of the following categories, select that category for direct access to the problem determination procedure. 3270 Emulation 5250 Emulation ACDI Common services Configuration DFT EHLLAPI Ethernet (ETHERAND) Host print Installation ISDN LUA PC Network Performance SDLC SNA (APPC, APPN) SRPI Subsystem management Token-ring Network Twinaxial X.25 ΓòÉΓòÉΓòÉ 2.3. Procedures ΓòÉΓòÉΓòÉ Select one of the following categories to begin problem determination. If you are not sure which category the problem is associated with, select Start Here. Start Here Problems Starting the Workstation Hardware Diagnostics Problems Starting Communications Manager FFST/2 Diagnostics Problems with Communications Manager Applications Operational Problems Running Communications Manager Problems Stopping Communications Manager Following Through ΓòÉΓòÉΓòÉ 2.3.1. Start Here ΓòÉΓòÉΓòÉ You are having problems with Communications Manager. Do you think you know the cause of the problem or the failing function or component and are you familiar with Communications Manager problem determination? ΓòÉΓòÉΓòÉ <hidden> Start Here ΓòÉΓòÉΓòÉ Select the Communications Manager component you believe may be causing the problem: 3270 Emulation 5250 Emulation ACDI Common services Configuration DFT EHLLAPI Ethernet (ETHERAND) Host print Installation ISDN LUA PC Network Performance SDLC SNA (APPC, APPN) SRPI Subsystem management Token-Ring Network Twinaxial X.25 If the problem does not fit any of the preceding categories, select Continue. ΓòÉΓòÉΓòÉ <hidden> Start Here ΓòÉΓòÉΓòÉ Improper cable connections, improperly configured adapters, CONFIG.SYS errors, or missing files can keep the workstation from starting. Does the workstation start correctly? ΓòÉΓòÉΓòÉ <hidden> Start Here ΓòÉΓòÉΓòÉ Improper configuration, insufficient resources, or missing files can keep Communications Manager from starting. Does Communications Manager start correctly? ΓòÉΓòÉΓòÉ <hidden> Start Here ΓòÉΓòÉΓòÉ Communications Manager application programs are programs that are not part of Communications Manager but use Communications Manager to perform a function. Do Communications Manager application programs start, run, and stop correctly? ΓòÉΓòÉΓòÉ <hidden> Start Here ΓòÉΓòÉΓòÉ Problems installing or configuring Communications Manager or problems with minimum hardware and software requirements can keep Communications Manager and its components from performing correctly. Does Communications Manager run correctly? ΓòÉΓòÉΓòÉ <hidden> Start Here ΓòÉΓòÉΓòÉ Unfinished processes using Communications Manager can keep Communications Manager from stopping when requested. Once started, does Communications Manager stop correctly? ΓòÉΓòÉΓòÉ <hidden> Start Here ΓòÉΓòÉΓòÉ The problem may be outside the scope of these procedures. Use the following general steps to try to solve any Communications Manager problem: 1. Check Communications Manager Components to see if your problem fits any of these categories. 2. Use FFST/2 to read any messages, errors, or alerts that may be associated with the problem (see FFST/2 Diagostics). 3. Use subsystem management to view the status of physical and logical links. Try to activate any inactive links. 4. Use CMRECORD to review your configuration and compare it with a working configuration. If you cannot solve the problem, select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ Symptom Explanation: You were able to start the workstation prior to installing Communications Manager, but now the workstation does not start. Possible Causes: o Hardware error o Hardware configuration error o Missing files Turn off the workstation and then turn it on again. Did a power-on self-test (POST) error occur? This is an error that occurs when the computer is counting up memory after being turned on. ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ A POST error usually indicates a hardware problem or a hardware configuration problem. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ Did a CONFIG.SYS error occur? This is an error that occurs when the computer is processing the CONFIG.SYS file. ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ If several CONFIG.SYS errors occurred, start with the first error. Did the error state that there are problems with the PROTOCOL.INI file? ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ Did the error state that the system was unable to find the PROTOCOL.INI file? ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ If the system found the PROTOCOL.INI file but reported errors, the PROTOCOL.INI file is probably corrupted. o If you cannot repair the existing PROTOCOL.INI file, reinstall and reconfigure Network Transport Services/2 (NTS/2). o If this does not correct the problem, select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ Did the error state that the system was unable to find a file? ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ Did the error state that the system could not open or initialize an adapter? ΓòÉΓòÉΓòÉ <hidden> Problems Starting the Workstation ΓòÉΓòÉΓòÉ Reinstall the missing file by selecting Communications Manager Setup from the Communications Manager/2 window and then selecting Reinstall... from Options on the menu bar. (You may need the Communications Manager diskettes.) If this does not work, you may need to reinstall Communications Manager by running Communications Manager Setup from Communications Manager diskette 1. Refer to Workstation Installation Guide for additional information. Select Continue. ΓòÉΓòÉΓòÉ 2.3.2. Hardware Diagnostics ΓòÉΓòÉΓòÉ The hardware installed on the workstation must be correct in order to adequately diagnose software problems. Do you suspect that the problem is with new hardware you recently added to your system? ΓòÉΓòÉΓòÉ <hidden> Hardware Diagnostics ΓòÉΓòÉΓòÉ Refer to the appropriate hardware documentation or repair organization. Note: If the workstation is a non-IBM system unit, refer to the manufacturer-provided documentation for the hardware. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Hardware Diagnostics ΓòÉΓòÉΓòÉ Perform the following tasks: 1. Attempt to run the failing operation on another Communications Manager-supported system. If the operation works on another system, suspect a hardware failure. As an alternative test, if you suspect that a particular hardware component is the cause of the problem, swap the suspected failing component with a working component on a machine with a similar configuration. If the problem occurs on the machine which was previously working, suspect a hardware failure. 2. Check all switches and personal computer hardware products attached to or installed in your computer to ensure that: o Power switches are on o Contrast and brightness controls are centered o Physical connections to the computer, including electrical outlets, cables, and power cords, are secure and functional o Installed options, such as adapters, are: - Designed for use with your system - Installed according to their instructions - Firmly connected Notes: Some devices that attach to your system, such as modems or printers, have test instructions of their own. Refer to the directions provided with those products when testing such attached devices. When you are running applications in more than one DOS or OS/2 session, performance degradation can result from certain problems associated with hardware configuration. If you suspect such a problem, refer to the discussion of hardware-related considerations in your OS/2 documentation. Does the problem still occur? ΓòÉΓòÉΓòÉ <hidden> Hardware Diagnostics ΓòÉΓòÉΓòÉ Run the online hardware diagnostics. o Use the procedures provided with your IBM Personal Computer AT or IBM Personal System/2 computer or compatibles. o If you suspect that a problem is associated with LAN hardware, such as an adapter, refer to the documentation that was shipped with the adapter that is installed on the workstation. According to the online hardware diagnostics, is the hardware functioning? ΓòÉΓòÉΓòÉ <hidden> Hardware Diagnostics ΓòÉΓòÉΓòÉ Refer to the appropriate hardware documentation or repair organization: o For an IBM Personal Computer AT, refer to Guide to Operations. o For an IBM Personal System/2 computer, refer to Quick Reference or Reference Diskette. o For other hardware devices, refer to local hardware personnel, procedures, or documentation. If you cannot correct the hardware problem, select Continue. ΓòÉΓòÉΓòÉ <hidden> Hardware Diagnostics ΓòÉΓòÉΓòÉ The problem is probably not hardware-related. You can: o Continue with the procedure that directed you to conduct hardware diagnostics (if you reached this procedure as a result of following instructions in another procedure). o Select Continue. ΓòÉΓòÉΓòÉ 2.3.3. Problems Starting Communications Manager ΓòÉΓòÉΓòÉ Symptom Explanation: You were able to start the workstation but you cannot start Communications Manager. Possible Causes: o Incorrect or missing configuration files o Insufficient resources o Missing required Communications Manager executable files o Missing statements in the CONFIG.SYS file Use subsytem management to determine if connectivity is established. (See Subsystem Management for more information.) Is connectivity established? ΓòÉΓòÉΓòÉ <hidden> Problems Starting Communications Manager ΓòÉΓòÉΓòÉ Communications Manager is started using the active configuration. If the configuration that is active is not the configuration you want, use CMSETUP to create a new configuration or modify an existing configuration. You can use CMREPL to specify which configuration is the active configuration. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems Starting Communications Manager ΓòÉΓòÉΓòÉ Did a pop-up message appear indicating that Communications Manager failed to start? ΓòÉΓòÉΓòÉ <hidden> Problems Starting Communications Manager ΓòÉΓòÉΓòÉ Try to start Communications Manager using subsystem management. If you are able to start the services you need by using this manual method, you probably have a problem with your STARTUP.CMD file. Refer to your OS/2 documentation for information on autostart. If you are not able to start Communications Manager using subsystem management, select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems Starting Communications Manager ΓòÉΓòÉΓòÉ Note the message number of the pop-up message and locate the corresponding message in the message log. Is the originator of the message CMKERNEL? ΓòÉΓòÉΓòÉ <hidden> Problems Starting Communications Manager ΓòÉΓòÉΓòÉ One of the following conditions probably occurred: o You have incorrect or missing configuration files. o You do not have enough resources to perform the requested task. o You are missing required Communications Manager executable files. If the pop-up message indicates a configuration problem, make sure that the configuration files you are expecting to use are in the \CMLIB directory. (Configuration files with the file extensions .cfg, .cf2, .ndf, and .sec must be present.) Also, check your invocation (autostart or command line) to make sure you invoke Communications Manager correctly. If you do not specify a configuration, make sure that the default configuration is the configuration you intend to use. Additionally, if the configuration uses a LAN, make sure that Network Transport Services/2 (NTS/2) (a separately orderable product) is installed and that the PROTOCOL.INI file exists in the \IBMCOM directory. If the pop-up message indicates a problem with resources (such as RAM or disk space), make sure that your system meets the minimum requirements for running Communications Manager as specified in Planning, Configuration, and Administration for Networks. If the pop-up message indicates that Communications Manager is missing required executable files, it is likely that a function was configured but not installed, or executable files were somehow deleted. You probably need to reinstall Communications Manager. Before you reinstall, however, use FFST/2 to check for other possible problems. Refer to Installation and Configuration Guide for information on installing Communications Manager. ΓòÉΓòÉΓòÉ 2.3.4. FFST/2 Diagnostics ΓòÉΓòÉΓòÉ Note: See FFST/2 for a detailed description of the services that FFST/2 provides. Did a pop-up message appear? ΓòÉΓòÉΓòÉ <hidden> FFST/2 Diagnostics ΓòÉΓòÉΓòÉ Perform the action indicated by the pop-up message and associated message help (if help is available). Did you correct the problem? ΓòÉΓòÉΓòÉ <hidden> FFST/2 Diagnostics ΓòÉΓòÉΓòÉ Note the time that the problem occurred so that you can refer to possible message log and error log entries. Any messages logged around the failure time may be relevant, especially if the originators are components you were using at the time of the failure. To save time, check for and read any associated messages before attempting to solve the problem. Are there any messages in the message log corresponding to the failure time? (See Accessing and Using the FFST/2 Message Log for more information.) ΓòÉΓòÉΓòÉ <hidden> FFST/2 Diagnostics ΓòÉΓòÉΓòÉ Any errors logged around the failure time may be relevant; especially if the originators are components you were using at the time of the failure. To save time, check for and read any associated error entries before attempting to solve the problem. Are there any error entries in the error log corresponding to the failure time? (See Accessing and Using the System Error Log.) ΓòÉΓòÉΓòÉ <hidden> FFST/2 Diagnostics ΓòÉΓòÉΓòÉ Locate and examine the problem determination information in the error log. (See Accessing and Using the System Error Log for more information.) If you are an experienced user, use the information in the error log to attempt to solve the problem; otherwise, select Continue. ΓòÉΓòÉΓòÉ <hidden> FFST/2 Diagnostics ΓòÉΓòÉΓòÉ Perform the action indicated by the message and message help. o If the message is associated with an error log and the message help instructs you to review the error log entry for additional information, see Accessing and Using the System Error Log. o If the message is associated with an alert and the message help instructs you to review the formatted alert for additional information, see Accessing and Using the FFST/2 Dump Formatter. Note: Key alert information is located at the beginning of the formatted dump. Select Continue. ΓòÉΓòÉΓòÉ 2.3.5. Problems with Communications Manager Applications ΓòÉΓòÉΓòÉ Symptom Explanation: You are able to start Communications Manager but you are having problems starting, running, or stopping a Communications Manager application program. Possible Causes: o Improper Communications Manager configuration o Hardware problem o Application program errors Use the following general hints for all application program problems: 1. Use FFST/2 Diagnostics to check for messages or errors. 2. Try to re-create the problem and trace the application program using the following trace selections (see Trace Services): Note: Consult your local support personnel before attempting to trace the application program. APIs: APPC. DLCs: Use the DLC event that corresponds to your communications medium. Events: APPC_CCB, APPC_INT, APPC_PROCESS, APPC_SNDRCV, APPC_XID, SERVICES_INT, and APPC_LOCAL_PATH. After you have gathered the trace data, determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. 3. Check to see if the problem fits any of the categories in Operational Problems Running Communications Manager. The following steps contain additional hints for more specific problems: Does the application program start correctly? ΓòÉΓòÉΓòÉ <hidden> Problems with Communications Manager Applications ΓòÉΓòÉΓòÉ Is this the first time you have tried to start the application program? ΓòÉΓòÉΓòÉ <hidden> Problems with Communications Manager Applications ΓòÉΓòÉΓòÉ The application was working previously. Someone may have modified either the configuration or the hardware. Check the date on the .cfg file to see if it has been recently modified. If you cannot correct the problem, select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems with Communications Manager Applications ΓòÉΓòÉΓòÉ Do the following: o Check the Communications Manager configuration. Make sure that the configuration is properly verified. Use FFST/2 to check VERIFY.LOG and make sure that there are no verification problems. See Message log and Accessing and Using the FFST/2 Message Log for more information. Use CMRECORD to see how the application program is defined to Communications Manager (see CMRECORD). o Check if there is a hardware problem. Check the cables and adapters. See Hardware Diagnostics to perform a complete hardware check. If applicable, repeat the previous configuration and hardware checks on the remote machine (consult your local support personnel if necessary). o Try to use the application on another workstation. o Check with other users or application programmers and make sure the application is configured correctly. If you cannot solve the problem, select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems with Communications Manager Applications ΓòÉΓòÉΓòÉ Does the application program run correctly? ΓòÉΓòÉΓòÉ <hidden> Problems with Communications Manager Applications ΓòÉΓòÉΓòÉ The application was running, but failed unexpectedly. o There may have been a link failure either locally or remotely. A message indicating an error or alert may have been logged. Use FFST/2 to check the message log. See Accessing and Using the FFST/2 Message Log for more information. o If you cannot correct the problem, select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems with Communications Manager Applications ΓòÉΓòÉΓòÉ Does the application program stop correctly? ΓòÉΓòÉΓòÉ <hidden> Problems with Communications Manager Applications ΓòÉΓòÉΓòÉ Press Ctrl + Esc to display the window list. Select the application you want to close and then select the system menu at the top left of the window list. Select Close to stop the application. If you continue to experience problems, check to see if the problem fits any of the categories in Operational Problems Running Communications Manager. If the problem is not covered by one of the categories, select Continue. ΓòÉΓòÉΓòÉ <hidden> Problems With Communications Manager Applications ΓòÉΓòÉΓòÉ If you continue to experience problems, check to see if the problem fits any of the categories in Operational Problems Running Communications Manager. If the problem is not covered by one of the categories, select Continue. ΓòÉΓòÉΓòÉ 2.3.6. Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Symptom Explanation: You are having problems running Communications Manager. Possible Causes: o Operational failures o User questions or difficulties o User programming problems o Performance problems Warning: Many steps in this procedure suggest that you perform in-depth problem determination such as tracing. If you are not familiar with Communications Manager problem determination techniques, you may want to contact your local support personnel before attempting these steps. Are you having Communications Manager configuration problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o For problems or questions during configuration, check the online helps available in each window. To get help for a specific field (for example, to determine the allowable characters in an input field), select the field to give it focus and press F1 or select Help. Next, press F2 or select General help to access general help for the window. Refer to Configuration Guide for detailed information on configuring Communications Manager. o For configuration verification errors or warnings: - If you are upgrading your configuration file from a previous version of Communications Manager, check the \CMLIB\UPGRADE.LOG file for messages. You must use the FFST/2 message log formatter (see Accessing and Using the FFST/2 Message Log) to view this log file. - If you are creating a new configuration or modifying an existing configuration, check the \CMLIB\VERIFY.LOG file for messages. You must use the FFST/2 message log formatter (see Accessing and Using the FFST/2 Message Log) to view this log file. - If you are using response files to create your configuration files, check the \CMLIB\CMRINST.LOG file for messages. This is an ASCII text file that can be viewed with an ASCII editor. - If the verification process ends with severe errors, but no relevant information is logged to VERIFY.LOG, check the default FFST/2 message log (OS2MLOG.DAT) for relevant verification messages. This situation can occur if the verification process is not able to find the active \CMLIB directory (for example, if CM.INI was deleted or renamed), or if a severe error occurs very early in the verification process. o If you edit your configname.NDF ASCII file to make configuration changes: - Check the APPNV.CTL file located in the active CMLIB directory for the syntax and examples of verbs in the configname.NDF file. - Be sure to run CMVERIFY to verify the configuration file every time you make a change to the configname.NDF file. The CMVERIFY /e option allows you to dynamically change certain SNA resources if Communications Manager is active and the configuration verifies successfully. - If you accidentally overwrite your configname.NDF file or want to restore it, use the APPNRST command to restore the configname.NDF file using the existing configname.CF2 file. o If you have a working configuration on another workstation, copy the working configuration to the failing workstation. Turn off the workstation with the working configuration and then test if the copied configuration works on the failing workstation. o Use CMRECORD to review the configuration and compare with a working configuration (if available). Refer to Configuration Guide for additional information on Communications Manager configuration. Refer to Planning, Configuration, and Administration for Networks for additional information on response file configuration. Refer to Command Reference for additional information on Communications Manager commands. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager installation problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. Also, check the installation audit trail file CM.LOG for information (select Options from the menu bar of the Communications Manager Setup window and select View audit trail...). If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o If you run out of space on the startup drive during installation, remember that you must have a minimum of five megabytes free storage on the startup drive before installing Communications Manager. o If you have configured Communications Manager and are beginning to install your configuration and run out of space, the Insufficient Space to Install window appears. This window allows you to: - Clean up your files and retry the installation - Select a different target drive o One way to save space on your installation drive is to not install additional functions (this can save up to six megabytes of disk space). o To use any LAN capability (such as IBM Token-Ring, PC Network, or Ethernet [ETHERAND]), you must have Network Transport Services/2 (NTS/2) (a separately orderable product) installed and configured. Check your \IBMCOM directory to see if the LANTRAN.LOG file is present. If you want to use any LAN capability and this file is not present, you must install and configure NTS/2. Refer to Installation and Configuration Guide for additional information on Communications Manager installation. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager 3270 emulation problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following hints: o Select Hardware Diagnostics to check your cables and connections. o Check that the physical link with the host is connected and active. If the physical link is not connected and active, no pop-up message appears and no message or error is logged. However, message numbers such as COMM695 are displayed in the Operator Information Area (OIA) at the bottom of the emulator window. You can look up these messages by selecting the system menu at the top left corner of the emulator window and then selecting Emulator help... followed by OIA message help (or you can look them up in Message Reference). Refer to IBM 3270 Information Display System: 3274 Control Unit Description and Programmer's Guide for additional information on messages displayed in the OIA. In many cases, you can correct emulator connectivity problems by rechecking your configuration to make sure that your network ID, local node name, local node ID, and LAN destination address are correct. After checking these, ask your host support personnel to make sure that the link is connected and active. Note: You can use CMRECORD to assist in checking your configuration (see CMRECORD for more information. o Refer to the host-to-PC parameter cross-reference tables in Host Connection Reference and Configuration Guide to check your configuration parameters. o Make sure your links to the host are active. Use the following procedure to display and activate the logical links: 1. From the Communications Manager/2 folder, select Subsystem Management. 2. From the Subsystem Management window, select SNA subsystem. 3. From the SNA Subsystem window, select Logical links and then select Details... from the menu bar. 4. From the Logical Links window, check the link status. If the link status is "Inactive," activate the link by selecting Link from the menu bar and then selecting Activate. o If you are using a token-ring network, check your LANTRAN.LOG file for errors. Ensure that the LAN connection is properly initialized. Also, make sure that your LAN destination address is unique and not used by another workstation. If you continue to experience problems, try to re-create the problem and trace 3270 emulation using the following trace selections (see Trace Services): APIs: LUA_RUI, LUA_SLI (for emulator client). DLCs: Use the DLC event that corresponds to your communications medium. For example: SDLC, IBMTRNET, or IBMPCNET. Events: Use the system events that correspond to your application. If you are having 3270 keyboard problems, use the following trace selections: APIs: None. DLCs: Use the DLC event that corresponds to your communications medium. For example: SDLC, IBMTRNET, or IBMPCNET. Events: 3270_1. After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager 5250 emulation problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagonstics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Select Hardware Diagnostics to check your cables and connections. o Check that the physical link with the host is connected and active. If the physical link is not connected and active, no pop-up message appears and no message or error is logged. However, message numbers such as COMM695 are displayed in the Operator Information Area (OIA) at the bottom of the emulator window. You can look up these messages by selecting the system menu at the top left corner of the emulator window and then selecting Emulator help... followed by OIA message help (or you can look them up in Message Reference). In many cases, you can correct emulator connectivity problems by rechecking your configuration to make sure that your network ID, local node name, local node ID, and LAN destination address are correct. After checking these, ask your host support personnel to make sure that the link is connected and active. Note: You can use CMRECORD to assist in checking your configuration (see CMRECORD). o If the UPM logon screen displays "Logon in Progress" or "Logon did not complete", make sure the link to the AS/400 (or S/36) is active. Use the following procedure to display and activate the logical links (see Communications Manager Subsystem Management for additional information): 1. From the Communications Manager/2 folder, select Subsystem Management. 2. From the Subsystem Management window, select SNA subsystem. 3. From the SNA Subsystem window, select Logical links and then select Details... from the menu bar. 4. From the Logical Links window, check the link status. If the link status is inactive, activate the link by selecting Link from the menu bar and then selecting Activate. One of the following may apply: - If you are using a LAN protocol and the link status briefly displays "Pending Active" before displaying "Inactive," you probably have an AS/400 configuration problem. Check with your host support personnel to determine if another controller definition on the AS/400 uses your Local LAN address but has a different local node name than what you have configured in Communications Manager. (The local node name for your workstation is referred to as the remote location name in the AS/400 controller description.) Check with your host support personnel to determine if the AS/400 is set up for automatic configuration of controllers and devices. If the AS/400 is not set up for automatic configuration of controllers and devices, your local support personnel must configure these for your workstation. If you are using non-LAN protocols, see Communications Manager Components and check the appropriate category for additional information. - If the link status displays "Pending Active" for an extended period of time before displaying "Inactive," check the LAN destination address to make sure entered the AS/400 address correctly. If you are using non-LAN protocols, check the appropriate section of Host Connection Reference or Configuration Guide for parameters that must match on the AS/400. If the parameters that are required to match are correct, check with your host support personnel to make sure the controller and devices for your workstation are "VARIED ON" at the AS/400. o Refer to the host-to-PC parameter cross-reference tables in Host Connection Reference and Configuration Guide to check your configuration parameters. o If you are using a token-ring network, check your LANTRAN.LOG file for errors. Make sure that the LAN connection is properly initialized. Also, make sure that your LAN destination address is unique and not used by another workstation. If you continue to experience problems, try to re-create the problem and trace 5250 emulation using the following trace selections (see Trace Services): APIs: APPC: DLCs: IBMTRNET, TWINAXIAL, ETHERAND, SDLC, or X.25. Events: APPC_CCB, APPC_INT, APPC_PROCESS, APPC_SNDRCV, APPC_XID, 5250_1, the events which correspond to your DLC (IBMTRNET, TWINAXIAL, ETHERAND, SDLC, or X.25_DLC), SERVICES_INT, and APPC_LOCAL_PATH. After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager SDLC problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following hints: o The R0CSDD.SYS device driver is required and must appear in the CONFIG.SYS before the SDLCDD.SYS device driver. o For SDLC DLC Adapter 0, you must have your reference diskette settings for the adapter set to SDLC_1, Arb 1 (arbitration 1). o For SDLC DLC Adapter 1, you must have your reference diskette settings for the adapter set to SDLC_2, Arb 7 (arbitration 7). Note: To use SDLC DLC Adapter 1, you must have two SDLC DLC adapters. If you do not have two SDLC DLC adapters and try to use SDLC DLC Adapter 1, you will get a secondary return code of ADAPTER_NOT_OPEN from APPC. If you continue to experience problems, try to re-create the problem and trace SDLC using the following trace selections (see Trace Services): APIs: None DLCs: SDLC: Events: SDLC: After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager EHLLAPI problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Check the EHLLAPI call return code. o Check the EHLLAPI call parameters. If you continue to experience problems, try to re-create the problem and trace EHLLAPI using the following trace selections (see Trace Services): APIs: EHLLAPI. DLCs: Use the DLC event that corresponds to your communications medium. Events: 3270_1 and 3270_2. After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager X.25 problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Verify that your X.25 adapter card has been installed and referenced correctly. o If an X.25 application programming interface (API) failure occurs, check that the slot number that contains the X.25 adapter card is referenced in your X.25 configuration file. o If X.25 Physical Link (X.25 API) is not "started" but "stopped" according to subsystem management, make sure that the device driver ICARICIO.SYS is present in \CMLIB and loaded in your CONFIG.SYS file. Also, make sure that ICAAIM.COM has been installed in the \CMLIB subdirectory from the X.25 options diskette (provided with the X.25 adapter card). o If X.25 Physical Link (X.25 API) is "started" according to subsystem management, check the X.25 Physical Links window. If the X.25 physical link displays "error level 1" or "error level 2" as the status, you probably have either a hardware problem or a configuration problem. Hardware: Check your cables, modem connections (if you are using a modem), network connections, and adapter card pins. Configuration: Local configuration definitions do not match either the network configuration, the host configuration (if you are connecting to a host), or the partner DTE's configuration. o If X.25 Physical Link (X.25 API) is "started" according to subsystem management, but the X.25 Logical Link is "stopped", select SNA subsystem and then select Logical links. If the link is not active, select Link from the menu bar and select Activate. If the link does not become active, you probably have a configuration problem (such as the parameters do not match). Check your SVC and PVC channel number definitions and make sure that they match your workstation. Also, check your directory entries and modem parameters. o Be sure to always check the Additional Parameters list. If you continue to experience problems, try to re-create the problem and trace X.25 using the following trace selections (see Trace Services): APIs: X_25. DLCs: X25_API Frame, X25_DLC. Note: The X25_DLC event can affect performance and may cause further problems. Use only if requested by IBM Service. Events: X25_API EVT_1, X25_API INTERNAL, X25_API QTHREAD, X25_DLC. For X.25 with SNA, use the following trace selections: APIs: X25_API, APPC. DLCs: The X25_DLC event can affect performance and may cause further problems. Use only if requested by IBM Service. Events: APPC_CCB, APPC_INT, APPC_PROCESS, APPC_SNDRCV, APPC_XID, and APPC_LOCAL_PATH. After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager SRPI problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, check your configuration and make sure it is configured for SRPI. If you continue to experience problems, try to re-create the problem and trace SRPI using the following trace selections (see Trace Services): APIs: SRPI. DLCs: Use the DLC event that corresponds to your communications medium. Events: SRPI_1, SRPI_2. After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager subsystem management problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. It is likely that what appears to be a problem with subsystem management is actually a problem with a Communications Manager subsystem. Subsystem management is used only for controlling Communications Manager subsystems and displaying their status. Check the category for the subsystem you are having problems with (see Communications Manager Components). See Communications Manager Subsystem Management for instructions on using subsystem management for problem determination. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager 3270 Host Print problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, consult your local support personnel or an experienced user and do the following hints: o Ensure that all of the definitions and configurations for your printer are correct. This includes making sure that definitions and configurations at the host application, VTAM/NCP, RSCS (VM only), Communications Manager printer sessions, Print Manager, and the printer are correct. o If the problem continues after you have ensured that all your definitions and configurations are correct, perform in-depth 3270 Host Print problem determination. This involves examining the data that is received by 3270 Host Print as input from the host and the data that 3270 Host Print sends to the spooler. To evaluate the data the host sends to 3270 Host Print, attempt to isolate the problem by performing and interpreting a trace of the Communications Manager data link control (DLC) interface. If, after interpreting the trace information, you have not found the problem but still suspect 3270 Host Print, use a binary editor on the spool file to evaluate the data that 3270 Host Print sends to the Print Manager spooler. Use the following steps to perform in-depth Host Print problem determination: 1. Put the print queue associated with the printer LU session in HOLD status. To put the print queue in HOLD status: a. Select the printer's icon from the desktop. b. Select the system menu on the printer's icon. c. Select Change status from the list. d. Select Hold from the additional menu list. 2. From the Trace Services window (see Trace Services), run a trace on the DLC function that you are using with the host printer LU session (for example, Token-Ring or SDLC). 3. Send a print job to Communications Manager. 4. After the job has completely spooled, stop the trace and save it to your disk. 5. Locate the spool file (xxxxxxx.SPL) and the spool header file (xxxxxxx.SHD) in the \SPOOL\printer_name directory. Note: xxxxxxx is a job number that is automatically generated. The .SPL file is the actual print job. The .SHD file contains header information. printer_name is the actual name of your printer icon on the desktop. Copy the .SPL and .SHD files to another directory (you may need them later in this procedure) and then release the job. 6. Interpret the Host Print trace by editing the trace file with an ASCII editor and examining exactly what the host sent to Communications Manager. At this point, neither Communications Manager nor 3270 Host Print has done any processing on the data. Note: EBCDIC to ASCII translation and formatting occur after the DLC trace is captured. If your print job has printer control codes in it (for example, if you are using PM_Q_RAW), examine the EBCDIC hexadecimal values for those control codes and check for any inacurracies. If the problem is seen in the trace file, it is likely that the problem is not with 3270 Host Print. Contact the application developer or your host system programmer. If you cannot find the problem by analyzing the trace file, but still suspect 3270 Host Print, analyze the spool file by performing the following step: Note: This step only works for functions that use the raw data path (PDT Alternative, ASCII PASSTHRU, and PM_Q_RAW. Files that use the raw data process function are simple ASCII text files. Files that use the standard data path are metafiles and cannot be easily examined. If you need help debugging problems with print jobs that use the standard data path, contact IBM. 7. Edit the spool file with a binary editor to display the actual hexadecimal characters. Look for the control codes or characters that are causing the problem. If the problem is present in the spool file but is not present in the trace, it is likely that the problem is with 3270 Host Print. Contact IBM Service. When you report the problem, mention that you have both the trace and the spool file. If you continue to experience problems, select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager common services problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Common services is primarily used as an application programming interface. Refer to Application Programming Guide for additional information. If you continue to experience problems, try to re-create the problem and trace common services using the following trace selections (see Trace Services): APIs: SERVICES. DLCs: None. Events: SERVICES_INT. After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager SNA (APPC, APPN) problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. Use CMRECORD to review your configuration (see CMRECORD for more information). If you continue to experience problems, try to re-create the problem and trace APPC using the following trace selections (see Trace Services): APIs: APPC. DLCs: Use the DLC event that corresponds to your communications medium. For example: SDLC, IBMTRNET, or IBMPCNET. Events: APPC_CCB, APPC_INT, APPC_PROCESS, APPC_SNDRCV, APPC_XID, SERVICES_INT, and APPC_LOCAL_PATH. After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager ACDI problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o If you have an IBM Personal Computer AT, make sure that the ASYNCDDA.SYS device driver statement is located in your CONFIG.SYS file. o If you have an IBM Personal System/2, make sure that the ASYNCDDB.SYS device driver statement is located in your CONFIG.SYS file. This device driver works for any IBM Personal System/2 but it does not take advantage of direct memory access (DMA), even if you have the DMA hardware available and active. o If you have an IBM Personal System/2 and have DMA hardware available and active, make sure that the ASYNCDDC.SYS device driver statement is located in your CONFIG.SYS file. DMA hardware must be enabled by using the IBM Personal System/2 Reference Diskette. If the DMA hardware is not available and active, you will not be able to use ACDI. Note: Switching to the ASYNCDDB.SYS device driver will allow you to use ACDI without using DMA. o If you want to use ACDI Redirection, make sure that the ASYNCDDE.SYS device driver statement is located in your CONFIG.SYS file. Refer to Command Reference for additional information on the REDIRECT command. Refer to Command Reference for additional information on device drivers. If you continue to experience problems, try to re-create the problem and trace ACDI using the following trace selections (see Trace Services): APIs: ACDI DLCs: None Events: None After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager Ethernet (ETHERAND) problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Check that Network Transport Services/2 (NTS/2) (a separately orderable product) isinstalled and configured. Check your \IBMCOM directory to see if the LANTRAN.LOG file is present. If you want to use any LAN capability and this file is not present, you must install and configure NTS/2. Note: You must have the proper level of the LAPS portion of NTS/2 installed. o Type \IBMCOM\LANTRAN.LOG and check for errors. Refer to your LAN documentation for descriptions of LAN errors. o You must have the ACSLANDD.SYS device driver statement in your CONFIG.SYS file (refer to Command Reference for additional information). o If you are using another LAN product and cannot start Communications Manager, try starting OS/2 without starting the other LAN product and then try to start Communications Manager. o Increase your resources in your NTS/2 configuration. If you continue to experience problems, try to re-create the problem and trace Ethernet (ETHERAND) using the following trace selections (see Trace Services): APIs: None DLCs: ETHERAND Events: None After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager PC Network problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Check that Network Transport Services/2 (NTS/2) (a separately orderable product) is installed and configured. Check your \IBMCOM directory to see if the LANTRAN.LOG file is present. If you want to use any LAN capability and this file is not present, you must install and configure NTS/2. Note: You must have the proper level of the LAPS portion of NTS/2 installed. o Type \IBMCOM\LANTRAN.LOG and check for errors. Refer to your LAN documentation for descriptions of LAN errors. o You must have the ACSLANDD.SYS device driver statement in your CONFIG.SYS file (refer to Command Reference for additional information). o If you are using another LAN product and cannot start Communications Manager, try starting OS/2 without starting the other LAN product and then try to start Communications Manager. o Increase your resources in your NTS/2 configuration. o If you are using PC Network and IBM Token-Ring Network simultaneously, check that your PC Network adapter card is configured as the primary adapter card and the Token-Ring adapter card is configured as the alternate adapter card. If you continue to experience problems, try to re-create the problem and trace PC Network using the following trace selections (see Trace Services): APIs: None DLCs: IBMPCNET Events: None After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager Token-Ring Network problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Check that Network Transport Services/2 (NTS/2) (a separately orderable product) is installed and configured. Check your \IBMCOM directory to see if the LANTRAN.LOG file is present. If you want to use any LAN capability and this file is not present, you must install and configure NTS/2. Note: You must have the proper level of the LAPS portion of NTS/2 installed. o Type \IBMCOM\LANTRAN.LOG and check for errors. Refer to your LAN documentation for descriptions of LAN errors. o You must have the ACSLANDD.SYS device driver statement in your CONFIG.SYS file (refer to Command Reference for additional information). o If you are using another LAN product and can not start Communications Manager, try starting OS/2 without starting the other LAN product and then try to start Communications Manager. o Increase your resources in your NTS/2 configuration. o If you are using PC Network and IBM Token-Ring Network simultaneously, check that your PC Network adapter card is configured as the primary adapter card and the Token-Ring adapter card is configured as the alternate adapter card. If you continue to experience problems, try to re-create the problem and trace Token-Ring using the following trace selections (see Trace Services): APIs: None DLCs: IBMTRNET Events: None After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager coaxial (DFT) problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Make sure that the DFTDD.SYS device driver statement is located in your CONFIG.SYS file. Refer to Command Reference for additional information. o If you are running LAN over coaxial cable, check that Network Transport Services/2 (NTS/2) is installed on your workstation. To find out if NTS/2 is installed, check the \IBMCOM directory for the LANTRAN.LOG file. o If you have two 3270 emulation cards, and are running both coaxial (DFT) and LAN over coaxial cable, make sure that the 3270 emulation card you are using for coaxial (DFT) has the lower slot number. o The 3270 emulation card has a set interrupt level of 2. If you simultaneously use other cards, you can avoid conflicts by setting their interrupt levels to something other than INT 2. Interrupt levels are set by using the reference diskette. If you continue to experience problems, try to re-create the problem and trace DFT using the following trace selections (see Trace Services): APIs: None DLCs: DFTDLC Events: None After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager Twinaxial problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Make sure that the appropriate device driver statement is located in your CONFIG.SYS file. - For twinaxial support on a workstation with an AT bus (IBM Personal Computer AT or IBM Personal System/2 Model 30 286), you must have the T1P1SDD.SYS device driver statement in your CONFIG.SYS file (refer to Command Reference for additional information). - For twinaxial support on a workstation with a microchannel bus (IBM Personal System/2 Model 50, 55, 60, 70, 80, 90, and 95), you must have the T1P1NDD.SYS device driver statement in your CONFIG.SYS file (refer to Command Reference for additional information). o Check your configuration and make sure your parameters are correct. Check with the host support personnel to determine which controller number you should specify in your TWINAX DLC profile. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager LU Application (LUA) problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, use the following list that describes some common LUA programming errors to assist you: o Reusing verb control block storage before the original verb completes This error occurs when two LUA verbs are issued and both use the same verb control block storage. Symptoms of this error include: - Verbs completing with undocumented primary or secondary return codes - Verbs completing unexpectedly You can avoid this problem by declaring 10 separate verb control block variables (one for each verb). If you use the SLI extension routines (BIND, CRV, SDT, and STSN), you may need to declare four more variables. o Failing to read all incoming messages and data An LUA application should attempt to read all data and messages from the host. Use RUI_READ or RUI_BID (or SLI_RECEIVE or SLI_BID) to accomplish this. If no LUA verb is outstanding when a session failure occurs or the data communication link fails, there is no way to tell the LUA application about the problem. LUA verbs are the only means of communication between LUA and the application program. If RUs from the host are not read, a RESPONSE OWED condition results. This condition can have undesirable effects. For example, a SLI_CLOSE normal converts to a SLI_CLOSE abend during a RESPONSE OWED condition. Symptoms of this error include: - An SLI_CLOSE normal was converted to SLI_CLOSE abend. - The LUA application was not notified of a session failure, protocol violation, or some other error. To avoid this problem, make sure that an RUI_READ or RUI_BID (or SLI_RECEIVE or SLI_BID) is outstanding at all times. A verb is outstanding when it returns with primary return code X'0030', IN_PROGRESS, which indicates that the verb will complete asynchronously. You can issue an initial RUI_BID (or SLI_BID) to complete when the first data arrives from the host. Then you can use RUI_READ (or SLI_RECEIVE) with lua_flag1 set to lua_flag1_bid_enable to read the data. Bid enable causes the RUI_BID (SLI_BID) to be reissued automatically to allow the verb to pick up the next piece of incoming data. The original RUI_BID (SLI_BID) must remain undisturbed during this process. o Failing to restart the session after session failure This error can occur because of one or both of the following: - The LUA application does not keep an RUI_BID or RUI_READ (or SLI_BID or SLI_RECEIVE) outstanding at all times, and cannot be told of a failure. Because the LUA application is not told of the failure, it does not issue RUI_INIT or SLI_OPEN to restore the session. - The LUA application does have a verb outstanding that returns primary return code X'000F', SESSION_FAILURE, or some other return code indicating a session failure or communication link failure, but the application does not issue RUI_INIT or SLI_OPEN to restart the session. Because of this error, the LUA application appears to be suspended. The LU-LU session is inactive and remains inactive. To correct this problem, make sure that an RUI_READ or RUI_BID verb (or SLI_RECEIVE or SLI_BID verb) is outstanding at all times. Verify that RUI_INIT or SLI_OPEN is issued where appropriate to restart the session. Refer to Conventional LU Application Programming Reference for additional information. If you continue to experience problems, try to re-create the problem and trace LUA using the following trace selections (see Trace Services): o For a summary LUA trace, select the following APIs, DLCs, and events: APIs: LUA_RUI, LUA_SLI. DLCs: Use the DLC event that corresponds to your communications medium. For example: SDLC, IBMTRNET, or IBMPCNET. Events: None. o For a detailed LUA trace, select the following APIs, DLCs, and events: APIs: APPC, LUA_RUI, LUA_SLI. DLCs: Use the DLC event that corresponds to your communications medium. For example: SDLC, IBMTRNET, or IBMPCNET. Events: APPC_CCB, APPC_INT, APPC_PROCESS, APPC_SNDRCV, APPC_XID, LUA. After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager ISDN problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. If no messages, error log entries, or alerts are associated with the problem, or if taking the action indicated did not solve the problem, do the following: o Check your cables and connections (especially if you are using CMCALL and received a cause code of 3426: Network Out of Order). o Make sure that the ISDN Co-Processor/2 adapter card and ISDN Co-Processor/2 Support Program are installed correctly for your network type. If you continue to experience problems, try to re-create the problem and trace ISDN using the following trace selections (see Trace Services): Note: ISDN events do not appear on the Trace Services windows unless ISDN is installed. Some ISDN events that register on the Trace Services windows are actually for another product (ISDN Co-Processor Support Program) that is a prerequisite for ISDN to function. APIs: IBM_CMGR_CMI, IBM_CMGR_GCCI, APPC DLCs: SDLC or X.25 DLC events (depending on which protocol you are using) Events: All APPC system events, IBM_CMGR MODULE, IBM_CMGR RETURN CODE, All ISB_ISDN events, SDLC or X.25 system events (depending on which protocol you are using) After you have gathered the trace data, contact your local support personnel to determine whether to interpret the trace data (see Unformatted Traces) or contact IBM. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ Are you having Communications Manager performance problems? ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ This is the last category. If your problem does not fit any of the other categories, use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts associated with the problem. Select Continue. ΓòÉΓòÉΓòÉ <hidden> Operational Problems Running Communications Manager ΓòÉΓòÉΓòÉ The problem could be associated with hardware or software. o If the hard disk light is on constantly, your machine may need more random access memory (RAM). You could also improve performance by upgrading the processor on your machine. o You can try to improve performance by running only the software that you currently need. o Are the request unit (RU) sizes sufficient for your application? These units of data should be as large as possible while taking into consideration the limitations of your connections (line noise). o Receive window counts must be sufficient for your application. o Refer to Configuration Guide for information on changing your RU size and receive window counts. o Refer to Planning and Migration Guide for minimum system requirements. Select Continue. ΓòÉΓòÉΓòÉ 2.3.7. Problems Stopping Communications Manager ΓòÉΓòÉΓòÉ Symptom Explanation: You are having problems stopping Communications Manager correctly. Possible Causes: o Processes are still using Communications Manager. Communications Manager cannot completely terminate until all processes using Communications Manager terminate. If you are having problems stopping Communications Manager, select Stop Communications Abnormally from the Communications Manager group. If problems persist and you want to try to isolate the problem, use the following procedure (otherwise, select Shutdown... from the desktop): 1. Type PSTAT /L on the OS/2 command line. The /L option of the PSTAT utility lists all currently active processes running in the system and shows their links. 2. Refer to your OS/2 documentation for instructions on stopping processes accessing a dynamic link library (DLL). 3. Use FFST/2 Diagnostics to locate and read any messages, error log entries, or alerts that may be associated with the problem. ΓòÉΓòÉΓòÉ 2.3.8. Following Through ΓòÉΓòÉΓòÉ Symptom Explanation: You have reached the final diagnostic procedure. Possible Causes: o You have corrected the problem o You have determined the cause of the problem o You did not determine the cause of the problem Did you correct the problem? ΓòÉΓòÉΓòÉ <hidden> Following Through ΓòÉΓòÉΓòÉ Did you determine the cause of the problem? ΓòÉΓòÉΓòÉ <hidden> Following Through ΓòÉΓòÉΓòÉ This diagnostic procedure is unable to help you determine the cause of the problem. You can: o Use your local support personnel to solve the problem o Ask your local support personnel to contact IBM ΓòÉΓòÉΓòÉ <hidden> Following Through ΓòÉΓòÉΓòÉ You have determined the cause of the problem. You can: o Use your local support personnel to solve the problem o Ask your support personnel to contact IBM. ΓòÉΓòÉΓòÉ <hidden> Following Through ΓòÉΓòÉΓòÉ You have corrected the problem. To minimize your problem determination efforts in the future, keep records of the solutions for all Communications Manager problems. ΓòÉΓòÉΓòÉ 3. First Failure Support Technology/2 (FFST/2) ΓòÉΓòÉΓòÉ FFST/2 is a software problem determination tool for OS/2 system software and applications. FFST/2 is designed to capture error data when the error occurs, provide immediate problem notification to predefined locations, and furnish unique error code identification. Because FFST/2 remains inactive until a software error is detected, impact on system performance is minimal. The services FFST/2 provides include: o Pop-up messages o A message log formatter o Access to the OS/2 system error log o A dump formatter o A message console o A command line interface for FFST/2 initialization and configuration Note: Most FFST/2 windows allow you to change the font and choose whether or not you want to see confirmation messages when you exit that window. These customizations are available from the menu bar when you select Options. See FFST/2 Diagnostics for instructions on using FFST/2 efficiently for problem determination. For more information, select one of the following categories: o Accessing and Initializing FFST/2 o Accessing and Using the FFST/2 Message Log o Accessing and Using the System Error Log o Accessing and Using the FFST/2 Dump Formatter o Accessing and Using the FFST/2 Message Console o Using the FFST/2 Command Line Interface ΓòÉΓòÉΓòÉ 3.1. Accessing and Initializing FFST/2 ΓòÉΓòÉΓòÉ FFST/2 is automatically installed with Communications Manager. To access FFST/2, select FFST/2 from the desktop. The FFST/2 folder appears, showing the following available selections: o Dump Formatter o Message Console o Message Log Formatter o System Error Log o Start FFST/2 o Stop FFST/2 Unless you modify the FFST/2 configuration, FFST/2 is automatically started when Communications Manager is started and no action is required on your part. If FFST/2 is not automatically started, select Start FFST/2 or type EPW at the OS/2 command line. You can automatically initialize FFST/2 at system startup by adding the EPW command to the CONFIG.SYS file. See Accessing and Using the FFST/2 Message Console for additional information on FFST/2 initialization. See Using the FFST/2 Command Line Interface for additional information on the EPW command. You can select Stop FFST/2 to disable FFST/2; however, if an error occurs, Communications Manager may start FFST/2 automatically. ΓòÉΓòÉΓòÉ 3.2. Accessing and Using the FFST/2 Message Log ΓòÉΓòÉΓòÉ The FFST/2 message log is the record of messages that are logged by FFST/2. The default name of this log is OS2MLOG.DAT. Communications Manager defines UPGRADE.LOG and VERIFY.LOG as additional message logs. See Message log for more information on the default message log and application-specific message logs. The FFST/2 message log is the focal point of Communications Manager problem determination. After viewing messages and information in this log, you can access related information in the system error log and dump formatter. Select one of the following categories: o Accessing the Message Log o Using the Message Log Formatter ΓòÉΓòÉΓòÉ 3.2.1. Accessing the Message Log ΓòÉΓòÉΓòÉ Select Message Log Formatter from the FFST/2 folder or type MSGLOGF at the OS/2 command line. The Open window appears. The Open window shows, by default, the message log 78file that is specified during FFST/2 configuration. o The easiest way to select a message log file to view is to double-click on one of the message log file names listed under Files. o If the desired message log file is in a directory other than the default, you need to select the appropriate directory to see the desired file. It is possible that no message log file exists in a particular directory. In this case, the Files field would be empty. o Select Help to obtain context-sensitive help. o The Directory is field is read only; it allows you to see long subdirectory names. o Only files identified as FFST/2 message log files appear under Files. o You can type any file name in the File Name entry field. The message log formatter ensures that the file is an FFST/2 message log file. Select a message log file and select Open. The Message Log Formatter window appears. Select Using the message log formatter to continue. ΓòÉΓòÉΓòÉ 3.2.2. Using the Message Log Formatter ΓòÉΓòÉΓòÉ After you have selected a message log file from the Open window, the Message Log Formatter window appears. The Message Log Formatter window contains a list of messages (on single lines in reverse chronological order). If a message is logged while you are viewing the message list, a "beep" sounds and the Refresh push button becomes highlighted. If you select Refresh, the log file is refreshed with a more recent list of messages. Note: Old messages may be deleted when the log is refreshed. Each entry in the message list contains the following message information: date, time, originator, message number, and the text of the message. You can view the information by using the horizontal scroll bar at the bottom of the window. By selecting File from the menu bar, you can return to the Open window, refresh the current message log list, print the details of a particular message, save the message log file under a new name, or exit the Message Log Formatter window. By selecting Options from the menu bar, you can search for a string in the message list, view the details of a selected message, or access the Search Criteria window. To view the details of a selected message, select Options and select Detailed Entry, or double-click on the message you want to view in the message list. The Full Details for Entry window appears. The Full Details for Entry window shows the most recent message record first. You can select Prev to view older records and select Next to view newer records. This window contains all the information of a single message log record in an easy-to-read format, including: Date: The date the message was logged. Time: The time the message was logged. Originator: The application that originated the message. Note: For Communications Manager, the originator is a component of Communications Manager. Refer to the online Message Reference for additional information about messages. Process ID: The OS/2 identifier for the process that originated the message. Message number: The 4-digit message number. Message type: The Message severity code. Valid values are: o I (Informational) o W (Warning) o E (Error) Process name: The name of the process that originated the message. Problem ID: The correlator you will use to find associated entries in the system error log and the FFST/2 dump formatter. Probe ID: The four-byte hexadecimal number that identifies the location of the internal software which captured data about the unexpected error condition. Message file name: The message file in which the text of the message is stored. Message text: The actual text of the message. Explanatory text: Any explanation or recommended action associated with the message. You can use the Entry Search Criteria window to selectively view messages in the message log. This is useful if you only want to view messages that have a certain originator or that occurred during a specified time frame. To access the Entry Search Criteria window, select Options from the Message Log Formatter window and then select Search Criteria. Specify any desired criteria to selectively view the logged messages and select OK. If you do not specify any criteria, all messages are displayed. To save the selected records of the message log under a different file name, select File from the Message Log Formatter window menu bar and select Save as, then specify a file name. To print the details of a message, select Print details from File on the Message Log Formatter window menu bar. This selection formats and prints (on the local printer) all the information contained in all of the message log records selected for display. Because this may take some time to complete, you have the option to cancel the print request at any time. ΓòÉΓòÉΓòÉ 3.3. Accessing and Using the System Error Log ΓòÉΓòÉΓòÉ The error log that FFST/2 uses is the OS/2 system error log. o This discussion of the OS/2 system error log is specific to OS/2 2.0. Refer to your OS/2 documentation if you are using another version of OS/2. o For the error log to be enabled, the following statements must be present in the CONFIG.SYS file: DEVICE=\OS2\SYSTEM\LOG.SYS RUN=\OS2\SYSTEM\LOGDAEM.EXE o For additional information on the OS/2 system error log, refer to OS/2 Command Reference. To access the system error log, select System Error Log from the FFST/2 folder or type SYSLOG at the OS/2 command line. The OS/2 Error Log Formatter window appears. The system error log shows the most recent record first. You can select Prev Rec to view older records and select Next Rec to view newer records. You can also use F7 for older records and F8 for newer records. You can also perform the following tasks from the OS/2 Error Log Formatter window: o Selecting error log records o Extracting Problem Determination information from the error log o Extracting Problem Report Form information from the error log o Printing error log records ΓòÉΓòÉΓòÉ 3.3.1. Selecting Error Log Records ΓòÉΓòÉΓòÉ You might want to limit the records you view to those records that occurred at a specified date and time or that had a particular qualifier. Use the following procedure to view selected records in the error log: 1. From the menu bar, select Options and select Display Options. The Log File Search Criteria window appears. 2. Use the Log File Search Criteria window to enter search criteria to select the error records you want to view. Enter a starting date and time or a unique qualifier to limit the number of records shown. 3. Press Display to display the most recent error log record that meets the search criteria you specified. The Error Log Formatter window reappears refreshed with records meeting the search criteria you specified. ΓòÉΓòÉΓòÉ 3.3.2. Extracting Problem Determination Information from the Error Log ΓòÉΓòÉΓòÉ The following fields in the error log contain information that is valuable in performing problem determination. Date and time of the error This information is useful when comparing information from other FFST/2 services and other diagnostic tools to get a complete picture of system occurrences at a particular time. Application name Name of the application that was running when the error occurred. Message number This is the number by which you can refer to information in an FFST/2 message log if a message is logged. For informational messages, the message number is not present in this field. See Extracting Problem Report Form information from the error log and refer to the description of the Symptom Data field to find out how to determine the message number for informational messages. Error code The first (or leftmost) eight digits are the major error code, and the remaining eight digits are the minor error code. For major error code 00000022, see OS/2 Request Codes for more information. Error originator This is the code which represents the Communications Manager function that reported the error. See Error Originators and Associated Functions for a list of valid Communications Manager error originators. Dump file name and alert status Shows the name of the dump file and whether the error log record is (Y) or is not (N) an alert. If the error log record is an alert, you can locate additional information by using the dump formatter. Problem ID This number allows you to easily correlate associated messages and errors. Look up a message in the message log, note the problem ID associated with that message, and check the error log for entries associated with that problem ID. This number is especially useful in situations where there are many entries in the error log. Additional Data Additional problem data provided by the application. The Additional Data section can consist of up to 16 columns of paired numbers. Each pair of numbers is a byte. The first pair of numbers on the first row is at offset 0. The first pair of numbers on the second row is at offset 16. The number of bytes associated with a field is referred to as the length. For example, if a message states that the error code is located in the Additional Data section at offset 2 with length 2, count pairs of numbers until you reach offset 2 and note that the two pairs (length) of numbers begining at offset 2 are the error code. Refer to the message associated with the error entry for information on deciphering this data for a specific error. ΓòÉΓòÉΓòÉ 3.3.2.1. Error Originators and Associated Functions ΓòÉΓòÉΓòÉ The following table correlates the Communications Manager function with the originator listed in the error log entry. Originator Associated Function ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ACDI Asynchronous Communications Device Interface ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ APPC SNA Communications Services ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ CMKERNEL Communications Manager Kernel ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ CONFIG Configuration Services ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ CPI-C Common Program Interface-Communications ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ DFTDLC Distributed Function Terminal Data Link Control ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ EHLLAPI Emulator High-Level Language Application Programming Interface ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ EMULATOR 3270/5250 Emulation ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ETHERAND ETHERAND Network ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ FILEXFER File Transfer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ HOSTGRAF 3270 Host Graphics ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ IBMPCNET PC Network ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ IBMTRNET IBM Token-Ring Network ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ INSTALL Installation Services ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ KEYLOCK Keylock ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LUA_RUI LU_Application Request Unit Interface ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LUA_SLI LU_Application Session Level Interface ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ RAS Problem Determination ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ SERVICES Common Services Utility ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ SDLC Synchronous Data Link Control ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ SNAGATE SNA Gateway ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ SRPI Server-Requester Programming Interface ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ SUBSYSM Subsystem Management ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ TWINAX Twinaxial DLC ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ UPGRADE Configuration Upgrade ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ VERIFY Configuration Verification ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ X25API X.25 API ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ X25DLC X.25 DLC ΓòÉΓòÉΓòÉ 3.3.3. Extracting Problem Report Form Information from the Error Log ΓòÉΓòÉΓòÉ You must complete a Problem Report Form before contacting IBM for service. The following fields in the error log contain additional information that is valuable for completing a Problem Report Form. Use these fields in addition to the fields discussed in Extracting Problem Determination Information from the Error Log to extract Problem Report Form information. MACHINE TYPE Machine type of your workstation. You specify this information in the FFST/2 Required Hardware Information window. If this field consists of blanks or zeros, or if you have a non-IBM workstation, supply the make and model of your workstation. S/N Serial number of your workstation. You specify this information in the FFST/2 Required Hardware Information window (see Entering Required Hardware Information). If this field consists of blanks or zeros, or if you have a non-IBM workstation, determine the serial number of your workstation. VERSION Application version number. SYMPTOM DATA Important information includes the product ID that is associated with the PIDS field and the probe ID that is associated with the PCSS field. The MS field can help you determine the message number for informational messages. In this field, the message prefix is followed first by a 0 and then by the message number. EXTRA SYMPTOM DATA This field contains problem-specific information that is useful for problem determination. Extra Symptom Data Codes describes codes that might be displayed in this field. ΓòÉΓòÉΓòÉ 3.3.3.1. Extra Symptom Data Codes ΓòÉΓòÉΓòÉ Code Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Adapter Adapter Number ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ API API Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Cause Cause Code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Check MACH/COMM/PROG Check Number ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Client Client Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ CodePage Code Page ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Connection Connection ID ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ConnNet Connection Network ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Conversation Conversation ID/Group Number ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Destination Destination Address ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Diagnostic Diagnostic Code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ DLC DLC Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ File File Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ FP FP Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Keyboard Keyboard Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LApp Local Application ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LLink Logical Link ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LLU Local LU Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ LLUAlias Local LU Alias ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Mode Mode Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ PID Process ID ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Port Port Number ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Profile Profile Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ PVC PVC Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Queue OS/2 Queue ID ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ RC Return Code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ RCP Remote CP Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ RC2 Secondary Return Code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ RLU Remote LU Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ RLUAlias Remote LU Alias ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Sense Sense Code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Server Server Name ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ServerAlias Server Alias ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Session Session Name/Number ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Slot Slot Number ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ TID Thread ID ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Unbind Unbind Type ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ User User ID ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ VController Virtual Controller ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Verb Verb Name ΓòÉΓòÉΓòÉ 3.3.4. Printing Error Log Records ΓòÉΓòÉΓòÉ If you want a printout of the error log for your records or to send with a Problem Report Form, do the following: 1. Use the Log File Search Criteria window to display the records you want to print. 2. From the Error Log Formatter window, select File and select Print. The Print window appears. 3. Make your printer selection and select Print. ΓòÉΓòÉΓòÉ 3.4. Accessing and Using the FFST/2 Dump Formatter ΓòÉΓòÉΓòÉ FFST/2 dumps are enabled and customized through FFST/2 configuration and are triggered when an error occurs. See Initializing and Configuring FFST/2 or Using the Command Line to Configure and Enable FFST/2 for more information about configuration parameters that affect dumps. To format and print dump data, select Dump Formatter from the FFST/2 folder or type EPWDF at the OS/2 command line. The Open window appears. The Open window shows, by default, a list of dump files that currently exist in the default dump directory as specified in FFST/2 configuration. You can select any of these files for formatting. Notes: o The easiest way to select a dump file to view is to double-click on one of the dump file names listed under Files. o EPWALERT.DMP is the dump file that contains alerts. o Select Help to obtain context-sensitive help. o The Directory is field is read only; it allows you to see long subdirectory names. o Only files identified as FFST/2 dump files appear under Files. o You can type any file name in the File Name field. The dump formatter ensures the file is an FFST/2 dump file. Select a dump file and select Open. The Dump Formatter window appears. You must maximize the Dump Formatter window to see all the information. The Dump Formatter window contains the following fields: o A selectable field that updates the formatted data of the dump when the entry title is changed o The date of the dump currently selected o The problem ID and the probe ID o The time of the dump currently selected o The dump file name o The originator of the dump currently selected o A scrollable list of appended dumps available for selection within the file o A scrollable list of entry titles available for display within the dump currently selected o The formatted data of the dump currently selected Note: You can access the FFST/2 dump formatter directly from the command line by entering EPWDF <file name> If no dump file name is specified, a standard Open window is displayed from which you can select a dump file name. There are several entry titles contained within each dump. To access the information under these different titles, first select the list box scrollable list of entry titles and then select the field that updates the formatted data to refresh the formatted data of the dump. The following entry titles may be contained within a customized dump: Note: Currently, Communications Manager uses the Generic Alert entry title of the FFST/2 dump formatter for formatting alerts. Other entry title descriptions are provided for your information only. Symptom Record This is the default entry that is normally displayed when you access the Dump Formatter window. This entry contains a formatted version of the information contained in the OS/2 system error log. CONFIG.SYS This entry contains a copy of key elements of your CONFIG.SYS file. Process Environment This entry contains basic information about the environment variables and the process that was running when the error occurred. Process Status Buffer This entry contains information about all processes running on the system. If the dump is an alert, the following entry is available: Generic Alert This entry contains formatted information about a problem or impending problem and identifies the cause of the problem and the component that caused the problem. ΓòÉΓòÉΓòÉ 3.5. Accessing and Using the FFST/2 Message Console ΓòÉΓòÉΓòÉ Use the message console when you want to view messages as they occur. Messages scroll through the window much like messages on a control console. Note: Communications Manager uses the message log formatter as the focal point for problem determination and message viewing. Use the message console for its FFST/2 configuration capabilities. Access the message console by selecting Message Console from the FFST/2 folder or by typing the command EPWCONS at the OS/2 command line. The Message Console window appears. Through the Message Console window you can: o Display messages o Initialize and configure FFST/2 o Specify required hardware information ΓòÉΓòÉΓòÉ 3.5.1. Displaying Messages ΓòÉΓòÉΓòÉ The message console maintains a scrollable list of all the messages displayed since the most recent restart of OS/2. By selecting File from the menu bar, you can save the message list to a file, print the message list, or exit the Message Console window. By selecting Options from the menu bar, you can find a search string in the message list, set word wrap on or off, access the Initialization and Configuration window, or access the Required Hardware Information window. ΓòÉΓòÉΓòÉ 3.5.2. Initializing and Configuring FFST/2 ΓòÉΓòÉΓòÉ The message console allows you to select FFST/2 initialization and configuration options and specify hardware data about your workstation. Select Options from the Message Console window menu bar and select Configuration.... The FFST/2 Initialization and Configuration window appears. You can use the FFST/2 Initialization and Configuration window to: o Turn FFST/2 on or off o Turn FFST/2 message pop-ups on or off o Configure the FFST/2 dump and message log file names The FFST/2 Initialization and Configuration window consists of the following fields and push buttons: o FFST/2 o Message pop-up o System o Application o Message log o OK o Cancel o Reset ΓòÉΓòÉΓòÉ 3.5.3. Specifying Required Hardware Information ΓòÉΓòÉΓòÉ The required hardware information you enter in this section is used to associate your workstation ID and your name with the alerts and customized dumps that are generated by your workstation. Information entered in this window is also used for the Machine Type and S/N fields in the system error log. To access the Required Hardware Information window, select Options from the Message Console window menu bar and select Hardware Information.... The Required Hardware Information window appears. Use the Required Hardware Information window to: o Enter your machine type and serial number o Specify your user-defined workstation ID o Enter your name, address, and phone number Note: The machine type and serial number fields are formatted for IBM machines only. If you are using a non-IBM machine, leave these fields blank or enter all zeros. ΓòÉΓòÉΓòÉ 3.6. Using the FFST/2 Command Line Interface ΓòÉΓòÉΓòÉ FFST/2 provides a command line interface that you can use instead of or in addition to the windowed interface. Some of these commands are fully functional commands, while others simply call up the Presentation Manager windows. Select one of the following: o Using the Command Line to Create the FFST/2 Folder o Using the Command Line to Configure and Enable FFST/2 o Using the Command Line to Route Alerts ΓòÉΓòÉΓòÉ 3.6.1. Using the Command Line to Create the FFST/2 Folder ΓòÉΓòÉΓòÉ The FFST/2 folder should already be created on your system. If it is not, type EPWINST on the OS/2 command line. This command causes a series of windows to be presented so that you can specify the FFST/2 configuration parameters and your workstation parameters. See Initializing and Configuring FFST/2 for instructions on negotiating the windowed interface. ΓòÉΓòÉΓòÉ 3.6.2. Using the Command Line to Configure and Enable FFST/2 ΓòÉΓòÉΓòÉ In addition to using the windowed interface, you can modify FFST/2 operations by executing the EPW command. This command allows you to: o Enable and disable FFST/2 o Enable and disable FFST/2 message display o Select the maximum number of dump data sets of a given type (either system dumps or application dumps) that may exist at one time in the current subdirectory for that type of dump o Select the subdirectory in which to place FFST/2 dump data files o Select the path and file name of the FFST/2 message log FFST/2 is enabled by the presence of an EPW command in the CONFIG.SYS file. All of the parameters for the EPW command are optional and may be specified in any combination or order. This command operates in two modes: 1. Initialization mode: FFST/2 has not yet been enabled. 2. Configuration mode: FFST/2 is enabled (ON) and new values for the parameters are being specified. ΓòÉΓòÉΓòÉ 3.6.3. Using the Command Line to Route Alerts ΓòÉΓòÉΓòÉ Alerts are generated when a severe error condition occurs. You can choose whether to route alerts to your alert log (EPWALERT.DMP), to the host (by SSCP-PU session), or to LAN Manager (if available). The default condition is to route alerts to the host. If you want to change the setting, use the EPWROUT command. On the OS/2 command line, type: EPWROUT -1 to route the alert only to your alert log EPWROUT 0 to not route the alert at all EPWROUT 1 to route the alert to the host EPWROUT 2 to route the alert to LAN Manager Alerts routed to the host or to LAN Manager are also logged in EPWALERT.DMP. An EPWROUT command remains active until you shut down your computer. You can modify the CONFIG.SYS file to permanently set EPWROUT to your preference. ΓòÉΓòÉΓòÉ 3.6.4. FFST/2 Command Summary ΓòÉΓòÉΓòÉ The following table lists the FFST/2 commands and their functions. Command Function ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ EPW Initializes and configures FFST/2 ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ EPWCONS Activates the message console ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ EPWDF Accesses the dump formatter ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ EPWINST Creates the FFST/2 folder ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ EPWROUT Tells FFST/2 which method of transport to use for alerts ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ MSGLOGF Accesses the message log formatter ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ SYSLOG Accesses the OS/2 system error log ΓòÉΓòÉΓòÉ 4. Trace and Dump Services ΓòÉΓòÉΓòÉ The Problem Determination Aids program available from the Communications Manager/2 folder on the desktop contains two tools for performing problem determination: Trace Services Records the sequence of events related to a communications application programming interface (API) and also records data related to a communications link. Dump Services Creates a copy of a selected portion of memory used by Communications Manager components. This chapter also contains examples of unformatted and formatted traces that can assist you when viewing traces. Select one of the following categories to view trace examples: o Unformatted Traces o Formatted Traces ΓòÉΓòÉΓòÉ 4.1. Trace Services ΓòÉΓòÉΓòÉ Trace Services records the sequence of events related to a communications application programming interface (API) and also records data related to a communications link. This record is referred to as a trace. Traces can be activated or deactivated through the window-driven Problem Determination Aids program or through the CMTRACE command. IBM Service or advanced users can analyze traces to identify and resolve Communications Manager problems. Application programmers can also use Trace Services to trace Communications Manager events that occur in their programs. Refer to Application Programming Guide for information on setting up traces to identify and resolve problems with application programs. Before using Trace Services, note the following: o Any prior-release autotrace selections you may have saved in your configuration are lost when you upgrade to Communications Manager Version 1.1. For Communications Manager Version 1.1, Trace Services functions independently of your configuration. You can start traces before you start Communications Manager. Once started, traces are active even after you exit the Trace Services window or restart your workstation. o When you are re-creating a communications problem to trace, stop and restart Communications Manager using the same configuration that was being used when communications problems occurred. o Record the time and date Communications Manager is started so that error and message log entries associated with re-creation of this problem can be identified and isolated by time and date. o Ensure minimal system activity when using Trace Services. Traces can be slowed or otherwise unintentionally affected by other active application programs. o Traces can be affected by application programs that include a DEFINE_TRACE or DEFINE_DUMP service verb. Refer to Application Programming Guide for a discussion of these verbs. o Select the trace selections before you re-create the problem. The selections are saved until you stop them. Also, make sure you write all selections you trace in the space provided on the Problem Report Form (Part B, question 3). o When you activate a dump, any active system or communications traces are stopped. The trace data is saved. The trace data is preserved in memory but must be saved to a file if needed later. o After traces are started, they are active until you select Stop or Stop All from the Trace Services window (even if you restart your computer). Select one of the following categories for more information: Performing a Trace Viewing the Trace Status Formatting a Trace File Changing Trace Buffer Defaults ΓòÉΓòÉΓòÉ 4.1.1. Performing a Trace ΓòÉΓòÉΓòÉ You can access Trace Services by selecting Problem Determination Aids - Trace Services from the Communications Manager/2 folder. You can use the Trace Services window to: o Select which product to trace o Select which trace selections for that product to trace o Select a path and file name for the trace file o Start selected traces o View active traces o View inactive traces o Stop selected traces o Stop all traces o Save the trace buffer o Clear the trace buffer Use the following procedure to perform a trace. 1. Select the product. From the list of items displayed, select the product you want to trace (Communications Manager is the default). 2. Select the trace selections. Select items from the following Trace selection categories: APIs DLCs Events 3. Select Start to start the selected traces. Additional Information for Start. 4. Select Stop All to stop all the selected traces after you have re-created the problem. Additional Information for Stop All. 5. Type the trace file name (use the extension .trc). Note: If you expect to have a very large amount of data, you should be sure the trace file will reside on a disk with sufficient available storage. Supply a path and filename for your trace file or select File from the menu bar. Select Select filename... to display the Filename Selection window. From the Filename Selection window, you can select a drive, directory, and file name for your trace file. The values in the fields default to the current drive and directory. a. To change the drive, select the arrow to the right of Drive and select from the list of items. b. To change the directory, double-click on the directory you want in the Directories list. c. To select a file name, click on the file name you want in the Files list or type a file name in the Filename entry field. When the file name you want is displayed in the Filename entry field, select OK. The Trace Services window reappears. 6. Select Save to save the trace data to the selected file name. Additional Information for Save. ΓòÉΓòÉΓòÉ 4.1.1.1. API Trace Selections ΓòÉΓòÉΓòÉ The valid choices for API trace selections are: ACDI APPC EHLLAPI LUA_RUI LUA_SLI MANAGEMENT SERVICES SPA_ROUTER SRPI X25_API ΓòÉΓòÉΓòÉ 4.1.1.2. DLC Trace Selections ΓòÉΓòÉΓòÉ The valid choices for DLC trace selections are: DFTDLC ETHERAND IBMPCNET IBMTRNET IDLC SDLC SPA_ROUTER TWINAXIAL X25_API FRAME X25_DLC ΓòÉΓòÉΓòÉ 4.1.1.3. Trace Events ΓòÉΓòÉΓòÉ The following is a complete list of system event numbers and their corresponding trace selections: Note: When using Problem Determination Aids - Trace Services windows, select the appropriate trace selections from the Events column. When using the CMTRACE command, specify the appropriate system event number. System Event Trace Selection 01 APPC_CCB 02 APPC_INT 03 APPC_PROCESS 04 APPC_SNDRCV 05 APPC_XID 06 ACDI 07 Reserved 08 Reserved 09 DFTDLC 10 IBMPCNET 11 SDLC 12 SERVICES_INT 13 SRPI_1 14 IBMTRNET 15 3270_1 16 3270_2 17 5250_1 18 5250_2 19 X.25_API EVT_1 20 X.25_DLC 21 TWINAXIAL 22 SRPI_2 23 X.25_API INTERNAL 24 X.25_API QTHREAD 25 LUA 26 Reserved 27 3270_GRAPHICS_1 28 3270_GRAPHICS_2 29 ETHERAND 30 SUBSYSM 31 APPC_LOCAL_PATH ΓòÉΓòÉΓòÉ 4.1.2. Viewing the Trace Status ΓòÉΓòÉΓòÉ From the Trace Services window menu bar, select Options and then select Trace Status Details.... The Trace Status Details window appears. This window displays status information using the following fields: RAS daemon Indicates whether the problem determination background process is active or inactive. Trace Indicates whether traces are active or inactive. Wrap count Indicates the number of times each trace buffer has been written to. For example, if you set the trace buffer size to 16 using the Trace Buffer Defaults window and Wrap count reads 1, all 16 trace buffers have been written to one time. As the trace continues, the data in the 16 trace buffers is overwritten. Note: Unsaved trace data has been overwritten when Wrap count has a value of one or greater. Segments allocated Indicates how many segments have been allocated for the trace. The number appearing in this field matches the trace buffer size defined in the Trace Buffer Defaults window. Current segment Indicates which of the allocated segments the trace is currently writing to. For example, if 10 segments have been allocated and Current segment reads 5, the trace is currently writing to the fifth of 10 segments. Offset into segment Indicates what position within the segment the trace is writing data to. This field tells you how much data has been written to the current segment. Trace notices This field can contain messages concerning the status of traces. If traces are stopped, you can reactivate them by selecting Start in the Trace Services window. The trace selections that were previously active will already be selected in the trace selections lists. ΓòÉΓòÉΓòÉ 4.1.3. Formatting a Trace File ΓòÉΓòÉΓòÉ Read the following information before using the Format Trace window. o You can use the Format Trace window to format an SNA trace file into an easier-to-use form. It formats trace records for the APPC API, APPC send events, and DLC data. You should format any traces that are SNA related. o The Format Trace window is based on the FMTTRACE command which is invoked from the command line. For information on the FMTTRACE command, see the online Command Reference. o Use caution if you are formatting trace files that were generated using a small trace record length (see Changing Trace Buffer Defaults for more information). Formatted records may contain incorrect data when a trace record is longer than the trace record length, and important fields are truncated. Use the following procedure to format a trace file. 1. Select File from the Trace Services menu bar and select Format Trace file.... The Format Trace window appears. 2. Select the parameters to format your trace file. o Trace input file defaults to the path and file name you selected from the Filename Selection window. You can type a different trace file name if you want. o Output file format You can produce two types of formatted output: a detail file (with one line per formatted field) and a summary file (in sequence diagram form with one line per trace event). You can select one or both of the following options: - Select Detail to produce a detail output file. This type of file has the extension DET. The default is not to produce a detail output file. - Select Summary to produce a summary output file. This type of file has the extension SUM. The default is to produce a summary output file. o Output formatted event type selection You can select one or more of the following options (All options are preselected as defaults): - Select API trace to format the API trace. - Select line flow trace to format the line flow trace. - Select CPI-C trace to format the CPI Communications trace. - Select Test RTS trace to format the Test RTS trace. o Selection of trace records based on ID Most APPC verbs have associated transaction program (TP) and conversation IDs. DLC data has an associated local form session identifier (LFSID) in the transmission header (TH). Trace records can be included or excluded from formatting, based on their ID. You can select one of the following options: - Select APPC API - TP ID to format the APPC API trace records with a TP ID matching X'xxxxxxxx'. (You supply the TP ID to search for.) - Select APPC API - conversation ID to format the APPC API trace records with a conversation ID matching X'xxxxxxxx'. (You supply the conversation ID to search for.) - Select DLC data - LSFID to format the DLC data trace records with a send LSFID matching X'xxxxx'. (You supply the LSFID to search for.) o Miscellaneous format options Select Uppercase hex to use uppercase alphabetic characters in hexadecimal output, such as X'BC2F'. (This is not the default.) If you want to use lowercase alphabetic characters in hexadecimal output, such as X'bc2f', select Uppercase hex so that the check box is not selected. (This is the default.) 3. Select Format after you have selected parameters to format the trace file. Note: Select Cancel if you do not want to format a trace file and want to exit the Format Trace window. ΓòÉΓòÉΓòÉ 4.1.4. Changing Trace Buffer Defaults ΓòÉΓòÉΓòÉ Communications Manager uses a buffer to store trace information. You can specify the size of this buffer from the Trace Buffer Defaults window. Use the following procedure to change trace buffer defaults: 1. Select Options from the Trace Services menu bar and select Trace buffer defaults.... The Trace Buffer Defaults window appears. 2. Select the Trace buffer size. If you require a storage size larger than the default of 64KB you can specify it from this window. Specify the storage size of the trace in multiples of 64KB segments. You can specify up to a maximum of 16 segments, which is equivalent to 1024KB of storage. 3. Select the Trace record length. You can change the record length from the default maximum of 12000. See Formatting a Trace File for possible consequences of changing this default. 4. Select Change after you have modified the trace buffer defaults to activate your changes. Note: Select Cancel if you do not want to change the trace buffer defaults and want to exit the Trace Buffer Defaults window. ΓòÉΓòÉΓòÉ 4.2. Dump Services ΓòÉΓòÉΓòÉ Dump Services creates a copy of a selected portion of memory used by Communications Manager components. This copy is referred to as a dump. IBM Service or advanced users can analyze dumps to identify and resolve Communications Manager problems. Application programmers can also use Dump Services to dump memory associated with Communications Manager. Refer to Application Programming Guide for information on setting up dumps to identify and resolve problems with application programs. Before using Dump Services, read the following information: o You should ensure minimal system activity when using Dump Services. o Running a 3270 or distributed function terminal (DFT) dump while other system activity is in progress can result in all DFT sessions being reset. o You should select the dump selections before you re-create the problem. The selections are saved until you exit Communications Manager. o When you activate a dump, any active system or communications traces are stopped. The trace data is preserved in memory but must be saved to a file if needed later. Access Dump Services by selecting Problem Determination Aids - Dump Services from the Communications Manager/2 folder. The Dump Services window appears. You can use the Dump Services window to: o Select which product to dump o Select which components of that product to dump o Select a path and file name for the dump file o Perform the dump Use the following procedure to perform a dump. 1. Select the product. From the list of items displayed, select the product you want to dump (Communications Manager is the default). 2. Select the component. From the list of items displayed, select the components you want to dump. 3. Type the dump file name (use the extension .dmp). Note: If you expect to have a very large amount of data, you should be sure the dump file will reside on a disk with sufficient available storage. Type a path and file name for your dump file or use the File menu bar option to access the Filename Selection window to specify an existing file name for your dump file. The values in the fields default to the current drive and directory. 4. Select OK to perform the dump. o Dump is not active until you have selected components. o If you have not selected a dump file name, the Filename Selection window appears. Supply a dump file name and select OK to continue the dump. The Dump in Progress window appears showing the status of the dump. Values in the fields change as the dump is performed. The dump process can take several minutes. You can stop the dump process at any time by selecting Stop. ΓòÉΓòÉΓòÉ <hidden> Start ΓòÉΓòÉΓòÉ o Start is not active until you have selected an item in the Trace selections list. o The selected traces are running in the background. o You can toggle between viewing the active and inactive traces by selecting Toggle view. o You can exit or minimize the Trace Services window while you attempt to re-create the problem. o If you want to start additional traces without affecting the traces you have already started, toggle to Viewing inactive traces and select the traces you want to start and select Start. The Trace Services window is refreshed with the active traces. o You can view the status of traces by using the Trace Status Details window. ΓòÉΓòÉΓòÉ <hidden> Stop All ΓòÉΓòÉΓòÉ o If you want to stop some traces and leave other traces active, toggle to Viewing active traces and select the traces you want to stop and select Stop. The Trace Services window is refreshed with the remaining active traces. o Stop All stops all traces, not just the selected traces. o Stop and Stop All can not be selected until you have started traces. o Stop and Stop All stop traces started from the Trace Services window or from the command line. o If you want to clear the trace buffer after stopping traces instead of saving the data to a file, select File from the menu bar and select Clear trace buffer. ΓòÉΓòÉΓòÉ <hidden> Save ΓòÉΓòÉΓòÉ o If you have not selected a trace file name, the Filename Selection window appears. Supply a trace file name and select OK to continue the save. o You can save trace data without stopping trace selections. This allows you to retain your trace selections and continue tracing while you examine a portion of the trace data. No trace data is lost. ΓòÉΓòÉΓòÉ 4.3. Unformatted Traces ΓòÉΓòÉΓòÉ This section contains examples of unformatted API and DLC traces that are supported by Communications Manager. Every API and DLC trace can be enabled by using any of the following features: o The Problem Determination Aids - Trace Services window o The CMTRACE command o The DEFINE_TRACE common services verb Each trace record begins with a header that contains the name of the trace and a time stamp of when the trace record was saved. The header may contain data specific to the trace type. The hexadecimal data for the trace record is listed after each header. To the right of the hexadecimal data is a character interpretation of that data. This section is enclosed by the less than (<) and greater than (>) signs. In addition, some traces format specific data contained in the trace record. Trace Services and Dump Services use the translation conventions shown in the following table to translate the hexadecimal data into displayable characters. A byte of hexadecimal data is represented by two consecutive hexadecimal digits ranging from 0 to F. The numbers in the left column of the table correspond to the first digit in a byte. The numbers in the top row correspond to the second digit in the byte. For example, the hexadecimal value 6E corresponds to n. Hexadecimal Translation Table for Trace Services and Dump Services ΓöîΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÉ Γöé Γöé0 Γöé1 Γöé2 Γöé3 Γöé4 Γöé5 Γöé6 Γöé7 Γöé8 Γöé9 ΓöéA ΓöéB ΓöéC ΓöéD ΓöéE ΓöéF Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé0 Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé1 Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé2 Γöé Γöé! Γöé" Γöé# Γöé$ Γöé% Γöé& Γöé' Γöé( Γöé) Γöé* Γöé+ Γöé, Γöé- Γöé. Γöé/ Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé3 Γöé0 Γöé1 Γöé2 Γöé3 Γöé4 Γöé5 Γöé6 Γöé7 Γöé8 Γöé9 Γöé: Γöé; Γöé< Γöé= Γöé> Γöé? Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé4 Γöé ΓöéA ΓöéB ΓöéC ΓöéD ΓöéE ΓöéF ΓöéG ΓöéH ΓöéI ΓöéJ ΓöéK ΓöéL ΓöéM ΓöéN ΓöéO Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé5 ΓöéP ΓöéQ ΓöéR ΓöéS ΓöéT ΓöéU ΓöéV ΓöéW ΓöéX ΓöéY ΓöéZ Γöé[ Γöé\ Γöé] Γöé^ Γöé_ Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé6 Γöé- Γöéa Γöéb Γöéc Γöéd Γöée Γöéf Γöég Γöéh Γöéi Γöéj Γöék Γöél Γöém Γöén Γöéo Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé7 Γöép Γöéq Γöér Γöés Γöét Γöéu Γöév Γöéw Γöéx Γöéy Γöéz Γöé{ Γöé| Γöé} Γöé= Γöé" Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé8 Γöé. Γöéa Γöéb Γöéc Γöéd Γöée Γöéf Γöég Γöéh Γöéi Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ Γöé9 Γöé. Γöéj Γöék Γöél Γöém Γöén Γöéo Γöép Γöéq Γöér Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ ΓöéA Γöé. Γöé. Γöés Γöét Γöéu Γöév Γöéw Γöéx Γöéy Γöéz Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ ΓöéB Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ ΓöéC Γöé. ΓöéA ΓöéB ΓöéC ΓöéD ΓöéE ΓöéF ΓöéG ΓöéH ΓöéI Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ ΓöéD Γöé. ΓöéJ ΓöéK ΓöéL ΓöéM ΓöéN ΓöéO ΓöéP ΓöéQ ΓöéR Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ ΓöéE Γöé. Γöé. ΓöéS ΓöéT ΓöéU ΓöéV ΓöéW ΓöéX ΓöéY ΓöéZ Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓö╝ΓöÇΓöÇΓöñ ΓöéF Γöé0 Γöé1 Γöé2 Γöé3 Γöé4 Γöé5 Γöé6 Γöé7 Γöé8 Γöé9 Γöé. Γöé. Γöé. Γöé. Γöé. Γöé. Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÿ Unformatted traces include: o API Traces o DLC Traces ΓòÉΓòÉΓòÉ 4.3.1. API Traces ΓòÉΓòÉΓòÉ This section contains examples of unformatted API event traces. Select one of the following trace categories: o ACDI API Trace o APPC API Trace o Common Services API Trace o CPI Communications API Trace o EHLLAPI API Trace o LUA API Trace o SRPI API Trace o Subsystem Management API Trace o X.25 API Trace ΓòÉΓòÉΓòÉ 4.3.1.1. ACDI API Trace ΓòÉΓòÉΓòÉ You can enable the Asynchronous Communications Device Interface (ACDI) API trace using any of the following methods: o Selecting ACDI from the API column of the Problem Determination Aids - Trace Services window o Using the CMTRACE command o Specifying the ACDI parameter of the DEFINE_TRACE common services verb Both the request and the return of a verb are traced. The header lines contain the following fields: o Request header line: API REQUEST ACDI verb address time stamp o Return header line: API RETURN ACDI verb address time stamp The time stamp indicates: hours:minutes:seconds:centiseconds (00:00:00:00) The address of the verb control block contains the selector, a separating colon, and the offset. If you call ACDI with a verb control block address that is not valid, the API trace data contains 6 bytes of zeros, starting at offset 13. If you call ACDI with a handle or function code that is not valid, no verb-specific data is traced after the first 18 bytes of data. The ACDI API trace contains the data listed in the following table. Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 5 PID = label in ASCII ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6 2 Process ID of process issuing verb ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8 5 CB = label in ASCII ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 13 1 Function code of the verb ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 14 1 ACDI version number ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 15 2 Return code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 17 2 Device handle ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 19 Variable Remainder of the verb control block Note: Data placed into the input and output buffers of the application is not traced. The following is an example of an ACDI API trace: API REQUEST ACDI 002F:23A0 11:19:08:06 50494420 3D202C00 4342203D 20020000 <PID = ,.CB = ...> 00000043 4F4D3100 20202003 <...COM1. . > API RETURN ACDI 002F:23A0 11:19:10:18 50494420 3D202C00 4342203D 20020000 <PID = ,.CB = ...> 00080043 4F4D3100 20202003 <...COM1. . > ΓòÉΓòÉΓòÉ 4.3.1.2. APPC API Trace ΓòÉΓòÉΓòÉ You can enable the Advanced Program-to-Program (APPC) API trace using any of the following methods: o Selecting APPC from the API column of the Problem Determination Aids - Trace Services window o Using the CMTRACE command o Specifying the APPC_API parameter on the DEFINE_TRACE common services verb The following example shows the first two lines of an APPC API REQUEST and an APPC API RETURN record. Each record is followed by a blank line. API REQUEST APPC 0E17:00C4 13:01:05:40 0C000100 00000000 00000000 770F393C <............w.9<> : : API RETURN APPC 0E17:00C4 13:01:05:43 0C000100 00140000 00000000 770F393C <............w.9<> : : API REQUEST: If you issue an APPC API, APPC adds an API REQUEST trace entry in the APPC SEND_DATA verb, operation code 0F00. API REQUEST APPC 0DA7:00FC 0F000000 00000000 00000000 A70E0822 074EC010 B70D0000 88130800 A71B0000 The following table shows an APPC verb control block. External verb control blocks are documented in APPC Programming Guide and Reference and System Management Programming Reference. APPC API Request Data Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 2 The first 2 bytes are the APPC operation code in hexadecimal. (The previous example shows operation code 0F00, which corresponds to a SEND_DATA verb.) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2 1 Basic conversation verbs are 00. Mapped verbs are 01. Nonconversation verbs are always 00. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 3 1 Reserved and always 00. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4 2 APPC primary return code. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6 4 APPC secondary return code. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 10 Variable The remainder of the verb control block. This is an example of the internal LUX_PASSTHRU verb, operation code 5000. The Communications Manager 3270 emulator issues this verb each time it sends a block of data. API REQUEST APPC 1337:0020 14:16:20:96 50000000 00000000 00001200 01000417 <P...............> 2714 <'. > API RETURN: The following API RETURN example shows the APPC CNOS verb, operation code 1500. It has a return code of 0003-00000005. API RETURN APPC 426F:0020 11:02:12:62 15000000 00030000 00054C55 34334330 <..........LU43C0> 31204C55 31324330 3120D4D6 C4C5F440 <1 LU12C01 MODE4.> 40400018 00000000 00 <......... > An API RETURN for APPC has the same format as a request; it is an APPC verb control block. APPC API Return Data Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 2 The first 2 bytes are the APPC operation code in hexadecimal. (The previous example shows an operation code 1500, which corresponds to a CNOS verb.) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2 1 Basic conversation verbs are 00. Mapped verbs are 01. Nonconversation verbs are always 00. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 3 1 Reserved and always 00. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4 2 APPC primary return code. In this example, the primary return code is 0003, indicating an allocate failure. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6 4 APPC secondary return code. The secondary return code is 000000005, indicating a retry. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 10 Variable The remainder of the verb control block. The following API RETURN example shows an MC_RECEIVE_AND_WAIT verb with a return code of 0000-00000000. Bytes 22 and 23 are X'0002', indicating DATA_COMPLETE. This field is not byte-swapped. API RETURN APPC 0E17:0020 13:04:00:84 0B000100 00000000 00000000 F70F4D3C <............7.M<> 646B201F 270E0002 00010000 06000600 <dk .'...........> 0000A718 00000000 00 <..x...... > ΓòÉΓòÉΓòÉ 4.3.1.3. Common Services API Trace ΓòÉΓòÉΓòÉ You can enable the Common Services API trace using any of the following methods: o Selecting SERVICES from the API column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the services_api parameter of the DEFINE_TRACE common services verb Both the request and the return of a verb are traced. The header lines contain the following fields: o Request header line: API REQUEST services verb address time stamp o Return header line: API RETURN services verb address time stamp The time stamp indicates: hours:minutes:seconds:centiseconds (00:00:00:00) The address of the verb contains the selector, a separating colon, and the offset. A Common Services API trace contains the data listed in the following table. Data in the Common Services API Trace Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 2 Verb operation code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2 1 Verb extension code (if any) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 3 1 Reserved (zero) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4 2 Primary return code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6 4 Secondary return code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 10 Variable Remainder of verb The following example shows a Common Services API trace: API REQUEST SERVICES 002F:0022 16:59:06:62 1F000000 00000000 00009E00 4D595047 <............MYPG> 4D202020 41435301 10001200 2F00 <M ACS...../. > API RETURN SERVICES 002F:0022 16:59:06:62 1F000000 00000000 00009E00 4D595047 <............MYPG> 4D202020 41435301 10001200 2F00 <M ACS...../. > ΓòÉΓòÉΓòÉ 4.3.1.4. CPI Communications API Trace ΓòÉΓòÉΓòÉ You can enable the CPI Communications API trace using any of the following methods: o Selecting APPC from the API column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the APPC_API parameter of the DEFINE_TRACE common services verb Enabling the CPI Communications API trace enables tracing of both CPI Communications calls and APPC verbs. The CPI Communications calls are described in Systems Application Architecture: Common Programming Interface: Communications Reference. Some CPI Communications calls cause the CPI Communications component to issue APPC verbs to complete the calls. In these cases, trace entries are recorded for both the CPI Communications calls and the APPC verbs. API REQUEST: The following example of an API request shows the CPI Communications Send_Data call (CMSEND). The variable values are shown in parentheses following the call name. The variable values are separated from each other by a comma. For an API REQUEST, only the values of input variables are shown; output variables are shown as a string of periods (........). The variable values, from left to right, correspond in order to the variables shown, top to bottom, in the call format illustrations in Systems Application Architecture: Common Programming Interface: Communications Reference. API REQUEST CPI-C CMSEND(08008F2D00000000,00028700 10:48:05:10 16000000,.....,........) 03000000 01000000 00000000 00000000 <................> 00000000 01000000 00000000 00000000 <................> 00000000 03000000 01000000 00000000 <................> 00000000 044D594C 55000000 00000659 <.....MYLU......Y> 4F55524C 55000000 00000000 00000000 <OURLU...........> 07D6E4D9 D4D6C4C5 0004D4E8 E3D70000 <.OURMODE..MYTP..> 00000000 00000000 00000000 00000000 <P...............> 00000000 00000000 00000000 00000000 <................> 00000000 00000000 00000000 00000000 <................> 00000000 00000000 00000006 E8D6E4D9 <............YOUR> E3D70000 00000000 00000000 00000000 <TP..............> 00000000 00000000 00000000 00000000 <................> 00000000 00000000 00000000 00000000 <................> 00000000 00000000 00000000 01400000 <................> 00000000 00 <..... > CMSEND buffer: C8819797 A840C289 99A38884 81A840E3 <Happy Birthday T> 9640E896 A45A <o YouZ > In the preceding example of CMSEND, the variables and their values are: Variable Value conversation_ID 08008F2D00000000 buffer 00028700 (address, byte-reversed) send_length 16000000 (byte-reversed) request_to_send_received ........ (output variable) return_code ........ (output variable) The buffer address is shown on the line with the CPI Communications call name. The buffer data is shown on a separate line, following the CPI Communications characteristics. The data immediately under the line with the CPI Communications call name shows the values of the entire set of CPI Communications conversation characteristics, as of the time the call was made. This set of CPI Communications characteristic values are included in the trace only with the following CPI Communications calls: o CMALLC, CMDEAL, CMPTR, CMRCV, CMSEND, and CMSERR, under the API REQUEST trace entry. These calls use one or more of the CPI Communications characteristics, as described in Common Programming Interface Communications Reference. o CMINIT and CMACCP, under the API RETURN trace entry. These calls initialize the CPI Communications characteristics. The following table lists the characteristic values. It shows the position (byte offset) of each characteristic in the trace, the CPI Communications pseudonym for the characteristic, and the length and type of the characteristic. The byte offset is given in decimal format. Trace Layout of CPI Communications Conversation Characteristics Byte Characteristic Length and Type Offset ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 conversation_state 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4 conversation_type 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8 return_control 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 12 deallocate_type 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 16 error_direction 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 20 sync_level 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 24 fill 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 28 prepare_to_receive_type 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 32 receive_type 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 36 send_type 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 40 conversation_security_type 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 44 log_data (address) 4-byte pointer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 48 log_data_length 4-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 52 local_LU_alias_length 1-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 53 local_LU_alias 8-byte character string ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 61 partner_LU_name_type 1-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 62 partner_LU_name_length 1-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 63 partner_LU_name 17-byte character string ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 80 mode_name_length 1-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 81 mode_name 8-byte character string ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 89 local_TP_name_length 1-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 90 local_TP_name 64-byte character string ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 154 TP_name_type 1-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 155 TP_name_length 1-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 156 TP_name 64-byte character string ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 220 user_ID_length 1-byte integer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 221 user_ID 8-byte character string All addresses, 2-byte, and 4-byte integer values are shown in the byte-reversed form, where the left-to-right order of bytes is from least significant to most significant. Both variable values and characteristics are stored in memory in byte-reversed format. In this example, the buffer address in normal segment:offset form is 251F:2010, and the send_length in normal integer notation is 16 (hexadecimal format, without the leading zeros). Character string values for the conversation characteristics are shown in left-to-right order of characters. When a character string is shorter than the field containing the string, the string is left justified and the trailing characters are disregarded. Some Additional Notes: o The characteristics shown in the preceding table are described in the CPI Communications Reference, except for the following: - local_LU_alias_length: The length of the local LU alias name. - local_LU_alias: The alias name of the local LU on which the CPI Communications TP instance is running. - local_TP_name_length: The length of the local TP name. - local_TP_name: The name of the local CPI Communications TP instance. o Some calls, such as the CMSEND in this example, have too many variables to fit on one line of the trace. In these cases, the line is split at column 64. The line may split in the middle of the variable value, just after a comma, just before a comma, or just before the ending parenthesis. o The Send_Data (CMSEND) and Receive (CMRCV) calls include the buffer variable. The trace entry for these calls shows the address of the variable on the call line. The content of the variable is shown starting on a separate line under the call. For CMSEND, the buffer content is shown in the API REQUEST trace entry. For CMRCV, the buffer content is shown in the API RETURN trace entry. o The Set_Log_Data (CMSLD) call includes the log_data variable. The API REQUEST trace entry for this call shows the address of the variable on the call line. The content of the variable is shown starting on a separate line under the call. The log_data variable supplies only the log data message, not the entire Error Log (X'12E1') GDS variable. Also, the content of the variable is shown in the ASCII encoding, as specified on the CMSLD call. o The Send_Error (CMSERR) and Deallocate (CMDEAL) calls may cause log data to be sent. If this occurs, the API REQUEST trace entry for these calls shows the log data on a separate line under the call. The entire Error Log (X'12E1') GDS variable is shown in its EBCDIC encoding. o The Define_CPIC_Side_Information (XCMSSI) and Display_CPIC_Side_Information (XCMESI) calls include the side_info_entry variable. The trace entry for these calls show the address of the variable on the call line. The content of the variable is shown starting immediately under the call line. For XCMSSI, the side_info_entry content is shown in the API REQUEST trace entry. For XCMESI, the side_info_entry content is shown in the API RETURN trace entry. o The all blank (X'40') mode_name is shown in the list of characteristics as a null value-all 0's (X'00') with a mode_name_length of 0. The security_password is not shown in any CPI Communications trace, in order to deter unintentional or deliberate discovery of security passwords. In particular: - The security_password is excluded from the list of characteristics, even when the conversation_security_type is XC_security_program (X'02000000' in the trace). - The security_password field in the side_info_entry structure on the Define_CPIC_Side_Information (XCMSSI) call is shown as all zeros in the trace entry, regardless of what value is really specified on the call. - The security_password variable on the Set_Conversation_Security_Password (XCSCSP) call is shown as all periods, regardless of what value is really specified on the call. API RETURN: An API RETURN for a CPI Communications call includes the values of the output variables. In the following example of the CMSEND call, the output variables are request_to_send_received and return_code. The request_to_send_received variable shows the value of 1 (X'01000000' in byte-reversed integer form), which is the value of cm_req_to_send_received. The return_code variable shows the value of 0 (X'00000000' in byte-reversed integer form), which is the value of cm_ok. API RETURN CPI-C CMSEND(08008F2D00000000,00028700,16000000 10:48:05:11 0100,0000,00000000) ΓòÉΓòÉΓòÉ 4.3.1.5. EHLLAPI API Trace ΓòÉΓòÉΓòÉ You can enable the Emulater High-Level Language Application Program Interface (EHLLAPI) API trace using any of the following methods: o Selecting EHLLAPI from the API column of Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specify the ehllapi parameter of the DEFINE_TRACE common services verb. Both the request and the return of a verb are traced. The first header lines contain the following fields: o Request header line: API REQUEST EHLLAPI verb name verb number time stamp o Return header line: API RETURN EHLLAPI verb name verb number time stamp The second header lines contain the following: o Request header line: ===> PS position length of Process/Thread extended error string IDs of caller information o Return header line: <=== Return code length of Process/Thread extended error string IDs of caller information The arrow pointing to the right indicates parameter values on call to EHLLAPI. The arrow pointing to the left indicates parameter values upon return from EHLLAPI. For a detailed explanation of EHLLAPI verb names, numbers, and corresponding parameters, refer to EHLLAPI Programming Reference. The following is an example of an EHLLAPI API trace: API RSP EHLLAPI Set Session Parameters (09) 11:59:47:90 <===RC=0000 LN=0004 ID=001F-0001 ER=0000-0000-0000 API REQ EHLLAPI Connect PS (01) 11:59:51:06 ===>RC=0000 LN=0004 ID=001F-0001 ER=0000-0000-0000 45 <E > API RSP EHLLAPI Connect PS (01) 11:59:51:21 <===RC=0000 LN=0004 ID=001F-0001 ER=0000-0000-0000 API REQ EHLLAPI Send Key (03) 11:59:51:25 ===>RC=0000 LN=0002 ID=001F-0001 ER=0000-0000-0000 4043 < C > API RSP EHLLAPI Send Key (03) 11:59:51:40 <===RC=0000 LN=0002 ID=001F-0001 ER=0000-0000-0000 API REQ EHLLAPI Send Key (03) 11:59:57:03 ===>RC=0000 LN=0014 ID=001F-0001 ER=0000-0000-0000 66696C65 6C697374 20787878 20797979 <filelist xxx yyy> 20614045 < a E > API RSP EHLLAPI Send Key (03) 11:59:57:25 <===RC=0000 LN=0014 ID=001F-0001 ER=0000-0000-0000 API REQ EHLLAPI Wait (04) 11:59:57:28 ===>RC=0000 LN=0014 ID=001F-0001 ER=0000-0000-0000 API RSP EHLLAPI Wait (04) 11:59:57:34 <===RC=0000 LN=0014 ID=001F-0001 ER=0000-0000-0000 API REQ EHLLAPI Find Field Position (31) 11:59:57:37 ===>RC=0001 LN=0014 ID=001F-0001 ER=0000-0000-0000 4E20 <N > API RSP EHLLAPI Find Field Position (31) 11:59:57:81 <===RC=0018 LN=0000 ID=001F-0001 ER=0000-0000-0000 ΓòÉΓòÉΓòÉ 4.3.1.6. LUA API Trace ΓòÉΓòÉΓòÉ You can enable the LUA API trace using any of the following methods: o Selecting LUA_RUI, LUA_SLI, or both from the API column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the rui_api parameter or the sli_api parameter (or both) of DEFINE_TRACE common services verb. The address of the verb control block contains the selector, a separating colon, and the offset. If you call LUA with a verb control block address that is not valid, the API trace data will contain 6 bytes of zeros, starting at offset 13. General LUA API Trace Record Header Line: The three types of LUA trace records are API REQUEST, API RETURN, and API POST. The originator is either LUA_RUI or LUA_SLI. The following example shows the header lines of the three types of LUA API trace records: API REQUEST originator verb address time stamp API RETURN originator verb address time stamp API POST originator verb address time stamp API REQUEST trace records are recorded when the LUA application program issues an LUA verb. API RETURN trace records are generally recorded when an LUA verb returns synchronously. API POST trace records are generally recorded when an LUA verb completes asynchronously. The verb control block field lua_flag2_asynch (offset byte 55) indicates whether a particular LUA verb completed synchronously or asynchronously. The verb address is the address of the LUA verb in memory. A sample verb address follows: 1ACF:0020 The meaning of the data in the sample verb address follows: 1ACF Selector 0020 Offset The time stamp is the system time when the trace record was recorded. A sample time stamp follows: 10:29:00:31 The meaning of the data in the sample time stamp follows: 10 Hours (10:00 a.m.) 29 Minutes 00 Seconds 31 Hundredths of seconds RUI API: The RUI API consists of six verbs. The following examples illustrate the first two lines of trace records for each RUI API verb. o Bytes 10 and 11 set to X'0180' indicate that this is an RUI_INIT verb. API POST LUA_RUI 1ACF:0020 10:29:00:31 52004000 00000000 00000180 00000000 <R...............> o Bytes 10 and 11 set to X'0280' indicate that this is an RUI_TERM verb. API REQUEST LUA_RUI 2DDF:040C 10:30:03:87 52004000 00000000 00000280 00000000 <R. .............> o Bytes 10 and 11 set to X'0380' indicate that this is an RUI_READ verb. API REQUEST LUA_RUI 2DDF:000C 10:29:05:46 52004000 00000000 00000380 00000000 <R. .............> o Bytes 10 and 11 set to X'0480' indicate that this is an RUI_WRITE verb. API RETURN LUA_RUI 2DDF:000C 10:29:08:46 52004000 00000000 00000480 00000000 <R. .............> o Bytes 10 and 11 set to X'0580' indicate that this is an RUI_PURGE verb. API RETURN LUA_RUI 2DDF:030C 13:46:42:96 52004000 00000000 00000580 00000000 <R. .............> o Bytes 10 and 11 set to X'0680' indicate that this is an RUI_BID verb. This RUI_BID returned with primary return code X'0030' (bytes 4-5), which indicates that the verb will complete asynchronously. An API POST trace record appears later in the trace for this verb, with the lua_flag2_asynch parameter set to ON. API RETURN LUA_RUI 01E7:04B8 15:05:56:03 52004C00 00300000 00000680 0000E701 <R.L..0........X.> SLI API: The SLI API consists of 10 verbs. The following examples illustrate the first two lines of trace records for the SLI API verbs. o Bytes 10 and 11 set to X'0100' indicate that this is an SLI_OPEN verb. API POST LUA_SLI 2D3F:0DF4 15:06:00:93 52004400 00000000 00000100 00000000 <R.D.............> o Bytes 10 and 11 set to X'0200' indicate that this is an SLI_CLOSE verb. API REQUEST LUA_SLI 2D9F:020C 15:06:13:31 52004000 00000000 00000200 00000000 <R. .............> o Bytes 10 and 11 set to X'0300' indicate that this is an SLI_RECEIVE verb. API REQUEST LUA_SLI 2D9F:010C 15:06:03:03 52004000 00000000 00000300 00000000 <R. .............> o Bytes 10 and 11 set to X'0400' indicate that this is an SLI_SEND verb. API REQUEST LUA_SLI 2D9F:020C 15:06:08:15 52004200 00000000 00000400 00000000 <R.B.............> o Bytes 10 and 11 set to X'0500' indicate that this is an SLI_PURGE verb. API RETURN LUA_SLI 2DDF:030C 15:06:08:45 52004000 00000000 00000500 00000000 <R. .............> o Bytes 10 and 11 set to X'0600' indicate that this is an SLI_BID verb. API RETURN LUA_SLI 2DDF:010C 10:24:19:78 52004C00 00300000 00000600 00000000 <R.L..0..........> o Bytes 10 and 11 set to X'1100' indicate that this is an SLI_BIND_ROUTINE verb. API REQUEST LUA_SLI 2D3F:050C 13:19:01:03 52004400 00000000 00001100 00000000 <R.D.............> o Bytes 10 and 11 set to X'1200' indicate that this is an SLI_STSN_ROUTINE verb. API RETURN LUA_SLI 2DDF:0DF4 15:06:00:93 52004400 00000000 00001200 00000000 <R.D.............> o Bytes 10 and 11 set to X'1300' indicate that this is an SLI_CRV_ROUTINE verb. API REQUEST LUA_SLI 2D3F:020C 15:06:01:50 52004400 00000000 00001300 00000000 <R.D.............> o Bytes 10 and 11 set to X'1400' indicate that this is an SLI_STD_ROUTINE verb. API REQUEST LUA_SLI 2D3F:020C 15:06:04:32 52004400 00000000 00001400 00000000 <R.D.............> Trace data contains a complete copy of the verb record and of the data buffer, if one is required. However, data placed into the input and the output buffers of the application is not traced. Refer to Conventional LU Application Programming Reference for more information. ΓòÉΓòÉΓòÉ 4.3.1.7. SRPI API Trace ΓòÉΓòÉΓòÉ You can enable the Server-Requester Programming Interface (SRPI) API trace using any of the following methods: o Selecting SRPI from the API column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the srpi_api parameter of the DEFINE_TRACE common services verb. Both the send data and the receive data are traced. The header line contains the following: o Request header line: API REQUEST SRPI time stamp o Return header line: API RETURN SRPI time stamp Each trace entry includes a header, trace data in hexadecimal format (on the left), and trace data in ASCII (on the right). When the words API REQUEST are displayed in the header, the trace entry represents an API invocation (or call). When the words API RETURN are displayed in the header, the trace entry represents an API return to the application. When the word SRPI is displayed in the header, SRPI is the API being invoked. The time stamp indicates: hours:minutes:seconds:centiseconds (00:00:00:00) The following table indicates how the hexadecimal information in each trace entry is interpreted. Data in the SRPI Trace Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 2 Process ID associated with the application process ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2 2 Thread ID associated with the application process ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4 1 Event type (X'01' indicates an API trace entry) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 5 1 Verb direction X'01' = Call; X'02' = Return ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6 104 CPRB The following example is of a trace entry created when a SEND_REQUEST verb is issued to server PERFSRV2 with 1000 (X'3E8') bytes of request parameters and 1000 (X'3E8') bytes of request data. The reply parameter length and reply data length indicate that up to 2000 (X'7D0') bytes of reply parameters and up to 2000 (X'7D0') bytes of reply data are expected to be received from the server. API REQUEST SRPI 08:13:34:81 0F000100 01016800 00010000 00000100 <......h.........> 00000000 E8030000 BF00E803 00009F00 <....Y.....Y.....> D0070000 CF00D007 0000AF00 00000000 <................> 00000000 00000000 00000000 00000000 <................> 00000000 00000000 00000000 00000000 <................> 00000000 00000000 00000000 00000000 <................> 00000000 08005045 52465352 56320000 <......PERFSRV2..> 00000000 00000000 00000000 00000000 <................> 00000000 00 <..... > The following example shows a trace entry created when control is returned to the application. The trace indicates that 2000 (X'7D0') bytes of reply parameters and 2000 (X'7D0') bytes of reply data were received from the server. API RETURN SRPI 08:13:36:90 0F000100 01026800 00010000 00000100 <......h.........> 00000000 E8030000 BF00E803 00009F00 <....Y.....Y.....> D0070000 CF00D007 0000AF00 00000000 <................> 0000D007 D0070000 00000000 00000000 <................> 00000000 00000000 00000000 00000000 <................> 00000000 00000000 00000000 00000000 <................> 00000000 08005045 52465352 56320000 <......PERFSRV2..> 00000000 00000000 00000000 00000000 <................> 00000000 00 <..... > ΓòÉΓòÉΓòÉ 4.3.1.8. Subsystem Management API Trace ΓòÉΓòÉΓòÉ You can enable the Subsystem Management API trace using any of the following methods: o Selecting MANAGEMENT from the API column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the subsysm_api parameter on the DEFINE_TRACE common services verb. Each trace entry includes a header, trace data in hexadecimal format (on the left), and trace data in ASCII (on the right). The header line contains abbreviations and symbols, which are defined as follows: API REQ An issued verb at the given address. API RET A completed verb at the given address. <=S== Data being sent. ==R=> Data being received. ORIG_ID The component being traced. A# The DLC adapter number. DESTINATION_ADDR The destination address for this link. ALS_ID_0000 The ALS_ID for this link. #: The size in hexadecimal format of the RU. TH The transmission header. RH The request or response header. (The second line and succeeding lines describe the RU in groups of 8hexadecimal digits, or 4 bytes.) ... Communications Manager has performed truncation according to the TRUNC specification. Both the request and return of the specific verb are traced. The time stamp indicates: hours:minutes:seconds:centiseconds (00:00:00:00) If more than one record is traced at once, only the first is time-stamped. The header line also contains the information indicated in the following trace example: API REQ ORIG_ID 5D00:20C6 12:43:45:68 2E007E3D 2E007E3D C620005D 01000000 <..==..==F .]....> 00000000 00000000 00000000 7E3D0A00 <............==..> 00000000 00000001 00000000 00000000 <................> 0000004C 55534944 4532204D 4F444531 <...LUSIDE2 MODE1> 20202008 54505349 44453241 20202020 < .TPSIDE2A > 20202020 20202020 20202020 20202020 < > <=S== ORIG_ID A# DESTINATION_ADDR ALS_ID__0000 12:43:46:65 #:6000 TH:2D000101000E RH:6B8000 31001307 B0B0D0B1 01008585 80010602 <1.........ee....> 00000000 00000000 20000008 4C555349 <........ ...LUSI> 44453120 28000902 4D4F4445 31202020 <DE1 (...MODE1 > 09030000 00000F00 00001204 41505043 <............APPC> 4E455420 4B4C5553 49444531 2000084C <NET KLUSIDE1 ..L> 55534944 453220 <USIDE2 .........> ==R=> ORIG_ID A# DESTINATION_ADDR ALS_ID__0000 12:43:46:34 #:4F00 TH:2D000101000E RH:EB8000 31001307 B0B0D0B1 01018585 81010602 <1.........eea...> 00000000 00000000 20000000 28000902 <........ ...(...> 4D4F4445 31202020 09030000 00000F00 <MODE1 ........> 00001205 41505043 4E455420 4B4C5553 <....APPCNET KLUS> 49444532 2000 <IDE2 ...........> API RET ORIG_ID 5D00:20C6 12:43:48:86 67007E3D 67007E3D C620005D 01000000 <g.==g.==F .]....> 00000000 00000000 00000000 7E3D0A00 <............==..> 00000000 CB3D0001 00000000 00000000 <.....=..........> 0000004C 55534944 4532204D 4F444531 <...LUSIDE2 MODE1> 20202008 54505349 44453241 20202020 < .TPSIDE2A > 20202020 20202020 20202020 20202020 < > ΓòÉΓòÉΓòÉ 4.3.1.9. X.25 API Trace ΓòÉΓòÉΓòÉ You can enable the X.25 API trace using any of the following methods: o Selecting X25_API from the API column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the x25_api_verbs parameter of the DEFINE_TRACE common services verb. Both the request and the return of the verb are traced. API request and return headers are followed by the X.25 verb control block at verb request and return times. The first 2 hexadecimal digits of the control block identify the verb type. Refer to X.25 Programming Reference for details about the contents of the control block for each verb type. If the verb has a data buffer, the X.25 verb control block is followed by the verb buffer at verb request time and at verb return time. The request header lines contain the following information: API REQUEST X25API Process ID verb time stamp Thread ID address Verb buffer X25API Process ID verb time stamp Thread ID address The return header lines contain the following information: API RETURN X25API Process ID verb time stamp Thread ID address Verb buffer X25API Process ID verb time stamp Thread ID address API REQUEST identifies a verb control block at request time. Likewise, API RETURN identifies a verb control block at return time. The verb control block address contains the selector, a separating colon, and the offset. The time stamp indicates: hours:minutes:seconds:centiseconds (00:00:00:00) The following is an example of an X.25 API trace: API REQUEST X25API 0019/0001 23BF:0008 09:47:57:09 10000000 00000000 00000000 0000DF23 <...............#> 80008000 05100101 00000000 20202020 <............ > 20202020 00000000 00000000 < ........ > Verb buffer X25API 0019/0001 23DF:0000 09:47:57:09 68656C6C 6F202020 20202020 20202020 <hello > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > API RETURN X25API 0011/0005 23BF:0008 09:47:57:40 10000000 00000000 00000000 0000DF23 <...............#> 80008000 05100101 00000000 00000000 <................> 00000000 00000000 00000000 <............ > Verb buffer X25API 0011/0005 23DF:0000 09:47:57:40 68656C6C 6F202020 20202020 20202020 <hello > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > ΓòÉΓòÉΓòÉ 4.3.2. DLC Traces ΓòÉΓòÉΓòÉ This section contains examples of unformatted DLC event traces. Select one of the following trace categories: o DLC Data o DFT DLC Trace o ETHERAND DLC Trace o IBM PC Network DLC Trace o IBM Token-Ring DLC Trace o SDLC DLC Trace o X.25 DLC Trace o X.25 Frame DLC Trace ΓòÉΓòÉΓòÉ 4.3.2.1. DLC Data ΓòÉΓòÉΓòÉ The following example shows the first two lines of a DLC SEND record and a DLC RECV record. Each record is followed by a blank line. <==SEND===== SDLC #00 0000E70E053C646B 13:01:38:15 #:000A TH:2F000103803A RH:CB8000 : : ===RECV====> IBMTRNET #00 40000012000004 0000B74ED04CAA63 14:10:41:81 #:0009 TH:2C000808803A RH:832000 : : Where: IBMTRNET This frame was sent on the IBMTRNET DLC. #00 This field is the adapter number in this machine that the frame was sent on. For token-ring network, it has a value of 00 or 01. 40000012000004 The first 6 bytes, X'400000120000', are the target token-ring adapter address of the remote machine. The final byte, X'04', is the LLC service access point (SAP) value. This field is blank for SDLC. 0000B74ED04CAA63 This field is a unique, internal adjacent link station identifier (ALS ID). The first 4 bytes are an OS/2 pointer (here 4EB7:0000, byte-reversed). The remaining 4 bytes are a value randomly generated by APPC to construct a unique ALS ID. Select one of the following categories to view examples of DLC event traces: o RH:009000, Data o RH:01A001, Data o RH:0A9100, Data o RH:009000, Incoming FM Header o RH:0B21A0, Incoming FM Header from CICS, with data o RH:4B8000, RTS Incoming o RH:4B9000, BIS o RH:6B8000, Incoming ACTPU o RH:6B8000, Outgoing BIND o RH:6B8000, Outgoing UNBIND o RH:830100, Isolated Pacing Response (IPR) o RH:832000, CONFIRMED verb issued o RH:838100, Positive Response, with pacing o RH:83A000, CONFIRMED verb issued o RH:879000, Reject of an FM Header o RH:CB8000, RTS response ΓòÉΓòÉΓòÉ 4.3.2.1.1. RH:009000, Data ΓòÉΓòÉΓòÉ The length of the data sent is X'0409' bytes, including the 6-byte TH and the 3-byte RH. <==SEND===== IBMTRNET #00 40000012000004 0000B74ED04CAA63 14:10:41:50 #:0409 TH:2C000808809D RH:009000 58585858 58585858 58585858 58585858 <XXXXXXXXXXXXXXXX> 58585858 58585858 58585858 58585858 <XXXXXXXXXXXXXXXX> : : ΓòÉΓòÉΓòÉ 4.3.2.1.2. RH:01A001, Data: ΓòÉΓòÉΓòÉ The length of the data sent is X'007C' bytes, including the 6-byte TH and the 3-byte RH. <==SEND===== IBMTRNET #00 40000012000004 0000B74ED04CAA63 14:10:41:50 #:007C TH:2C000808809E RH:01A001 58585858 58585858 58585858 58585858 <XXXXXXXXXXXXXXXX> 58585858 58585858 58585858 58585858 <XXXXXXXXXXXXXXXX> 58585858 58585858 58585858 58585858 <XXXXXXXXXXXXXXXX> : : ΓòÉΓòÉΓòÉ 4.3.2.1.3. RH:0A9100, Incoming FM Header ΓòÉΓòÉΓòÉ This example shows an incoming attach RU trace. ===RECV====> SDLC #00 #:002F TH:2C0007010001 RH:0A9100 120502FF 0003D000 0007E4C1 D3E3D7E2 D9000014 12020100 3C002C01 00005541 4C4C5531 2020 The following list describes the fields for an incoming attach RU trace: Field Description #:002F This field is the number of bytes sent. This number includes the 6-byte TH and the 3-byte RH fields. RH:0A9100 In bit format, the first byte of the RH, X'0A', is: 00001010. Note that the fifth bit, the FI bit, is 1. This value indicates that an FM header follows. Refer to the description of FM Headers in Systems Network Architecture Network Product Formats for further information. 12 This field is the length of the FM header, in hexadecimal format, including the length byte. 05 This field is an FM header type 5 (an FMH-5). 02FF This field is an attach RU. 00 This field indicates no security or PIP data. 03 This byte is always 03 on an Attach. D0 Basic conversation. 00 This field is reserved; always 00. 00 Sync level = none. 07 This field is the length of the transaction program name, in hexadecimal format. A transaction program name can be up to 64 bytes long; trailing blanks are truncated in an Attach. E4C1D3E3D7E2D9 The transaction program name, in EBCDIC. This field translates to UALTPSR. If this name is X'06F1' (and the preceding byte is length X'02'), it indicates that this is the internal transaction program used for CNOS exchange to maintain parallel sessions. ΓòÉΓòÉΓòÉ 4.3.2.1.4. RH:0B21A0, Incoming FM Header from CICS, with data ΓòÉΓòÉΓòÉ This example shows a trace FM header from CICS and the associated data. ===RECV====> IBMTRNET #00 40000031740104 60509F16CE5F99C7 14:19:30:46 #:0087 TH:2C0001010002 RH:0B21A0 2A0502FF 0003D100 4008D9C3 E5C6C9D3 <*.....J. .RCVFIL> C5400011 08C3C9C3 E2C24040 405D2037 <E ...CICSB ] 7> 7C60C600 010460F9 F9F90054 12FFD5C1 <|-F...-999.T..NA> D4C5F440 40404040 40404040 40404040 <ME4 > 40404040 40404040 40404040 40404040 < > 40404040 40404040 40404040 40404040 < > 40404040 40404040 40404040 40404040 < > 40404040 40404040 40404040 4040 < > The following list describes the fields for an incoming FM header from CICS. Field Description #:0087 This field is the number of bytes sent. This number includes the 6-byte TH and the 3-byte RH fields. RH:0B21A0 In bit format, the first byte of the RH, X'0B', is 00001011. Note that the fifth bit, the FI bit, is 1. Refer to the description of the FM Headers in Systems Network Architecture Network Product Formats for further information. 2A This field is the length of the FM header, in hexadecimal format, including this length byte. 05 This field is an FM header type 5 (an FMH-5). 02FF This field is an attach RU. 00 This field indicates no security or PIP data. 03 This byte is always 03 on an Attach. D1 Mapped conversation. 00 This field is reserved; always 00. 40 Sync level = confirm. 08 This is the length of the Transaction Program Name field, in hexadecimal format. A transaction program name can be up to 64 bytes long. If there are trailing blanks, they may be truncated in the Attach, depending on APPC implementation of the sending machine. D9C3E5C6CC540 The transaction program name, in EBCDIC. This field translates to RCVFILE. Some systems pad the name with a blank, as shown here, while others do not. 00 No Access Security Information field. 11 Length of the Logical-Unit-of-Work Identifier field. 08 Length of the network-qualified LU name. C3C9C3E2C2404040 Network-qualified LU network name. 5D20377C60C6 Logical-unit-of-work (LUW) instance number. 0001 Logical-unit-of-work (LUW) sequence number. 04 Length of conversation correlator. 60F9F9F9 Conversation correlator. 0054 LL field for the mapped conversation data. 12FF GDS header for the mapped conversation data. D5C1... Mapped conversation application data. ΓòÉΓòÉΓòÉ 4.3.2.1.5. RH:4B8000, RTS incoming ΓòÉΓòÉΓòÉ This example shows a Request_to_send incoming trace. ===RECV====> SDLC #00 0000E70E053C646B 13:01:38:12 #:000E TH:2F000301803A RH:4B8000 C9000100 01 <I.... > The partner issued a REQUEST_TO_SEND verb. If your transaction program now issues a TEST_RTS verb, it is successful. ΓòÉΓòÉΓòÉ 4.3.2.1.6. RH:4B9000, BIS ΓòÉΓòÉΓòÉ This example shows an incoming Bracket Initiation Stopped (BIS) trace. After a BIS is received, an UNBIND should be the next flow received from the remote node. <==SEND===== IBMTRNET #00 10005A010BE204 0000D70AEA266FC3 11:54:56:25 #:000A TH:2E0001010002 RH:4B9000 70 <p > ΓòÉΓòÉΓòÉ 4.3.2.1.7. RH:6B8000, Incoming ACTPU ΓòÉΓòÉΓòÉ This trace example shows an incoming ACTPU. An ACTPU is indicated by a X'11' in the first byte of the data field. ===RECV====> IBMTRNET #00 40001300008104 0000BF4315919B6F 17:17:49:56 #:0012 TH:2D0000006B6D RH:6B8000 11020105 00000012 40 <......... > Field Description 11 For information on this field, refer to ACTPU in the list of SC Request Codes in the Systems Network Architecture Network Product Formats. 02 Format 0, ERP activation type. 01 FM profile 0, TS profile 1. 050000001240 ID of the SSCP issuing ACTPU. The X'05' indicates the sender is a PU type 5. The remaining 5 bytes are implementation dependent. ΓòÉΓòÉΓòÉ 4.3.2.1.8. RH:6B8000, Outgoing BIND ΓòÉΓòÉΓòÉ This example shows an outgoing BIND trace. A BIND is indicated by a X'31' in the first byte of the data field. <==SEND===== IBMPCNET #00 50000000004404 0000D742FC8F9161 11:02:49:09 #:006F TH:2F0001018FFE RH:6B8000 31001307 B0B0D0B1 08008787 80080602 <1.........gg....> 00000000 00000000 23000010 E3D9D5D5 <........#...TRNN> C5E3F0F1 4BD3E4F4 F3C3F0F1 27000902 <ET01KLU43C01'...> E2D5C1E2 E5C3D4C7 0903008F 9161FF8F <SNASVCMG....ja..> 91611104 E3D9D5D5 C5E3F0F1 4BD3E4F4 <ja..TRNNET01KLU4> F3C3F0F1 0010E3D9 D5D5C5E3 F0F14BD3 <3C01..TRNNET01KL> E4F4F4C3 F0F1 <U44C01 > Field Description RH:6B8000 This field is RU category 11 (the middle 2 bits of the first nibble), which is session control (SC) information. 31 For information on this field, refer to BIND in the list of SC Request Codes in Systems Network Architecture Network Product Formats. 001307 This field is always 001307 for LU 6.2. B0B0 Primary and secondary LU protocols. For more information on these bit-significant fields, refer to Systems Network Architecture Network Product Formats. D0B1 Common LU protocols. For information on these bit-significant fields, refer to Systems Network Architecture Network Product Formats. 0800 TS usage: Secondary to primary pacing stages is 1. Secondary send window size is 8. Adaptive pacing is not supported. Secondary receive window size is 0. 8787 Maximum RU size. Secondary maximum send RU size is 1024. Primary maximum send RU size is 1024. 8008 Primary to secondary pacing stages is 1. Primary send window size is 0. Primary receive window size is 8. 0602 Always 0602 for LU 6.2. 00000000000000 Reserved (7 bytes). 00 No conversation security accepted and not already verified. 23 Confirm and parallel sessions supported. 00 Reserved. ΓòÉΓòÉΓòÉ 4.3.2.1.9. RH:6B8000, Outgoing UNBIND ΓòÉΓòÉΓòÉ This example shows an outgoing UNBIND trace. The second byte of the data field is X'FE', which indicates session failure. <==SEND===== IBMTRNET #00 40000012000004 0000B74ED04CAA63 14:10:41:81 #:000F TH:2D00080850D2 RH:6B8000 32FE200E 0000 <2. ... > Field Description RH:6B8000 This field is RU category 11 (the middle 2 bits of the first nibble), which is session control (SC) information. 32 For information on this field, refer to UNBIND in the list of SC Request Codes in Systems Network Architecture Network Product Formats. FE Indicates the UNBIND type. Type X'FE' is session failure due to protocol violation. 200E0000 Sense data is only included here for UNBIND type X'FE'. This field indicates: "Response Correlation Error: A response was received that cannot be correlated to a previously sent request." This example shows an outgoing normal UNBIND. The second byte of the data field is X'01', which indicates a normal UNBIND. <==SEND===== SDLC #00 00000714C3AA3564 14:16:25:87 #:000B TH:2D0001020000 RH:6B8000 3201 <2. > ΓòÉΓòÉΓòÉ 4.3.2.1.10. RH:830100, Isolated Pacing Response (IPR) ΓòÉΓòÉΓòÉ This example shows an incoming Isolated Parsing Response trace. ===RECV====> IBMTRNET #00 40000012000004 0000B74ED04CAA63 14:10:41:62 #:0009 TH:2C0008088091 RH:830100 The RH of an IPR is always 830100. This frame corresponds with a previously sent frame that should have the same TH field (except bytes 3 and 4, the OAF and DAF, are swapped). ΓòÉΓòÉΓòÉ 4.3.2.1.11. RH:832000, CONFIRMED verb issued ΓòÉΓòÉΓòÉ This example shows a trace with a CONFIRMED verb. ===RECV====> IBMTRNET #00 40000012000004 0000B74ED04CAA63 14:10:41:81 #:0009 TH:2C000808803A RH:832000 The RH indicates RQD2, with a positive response. This frame corresponds with a previously sent frame that should have the same TH field (except bytes 3 and 4, the OAF and DAF, are swapped). ΓòÉΓòÉΓòÉ 4.3.2.1.12. RH:838100, Positive Response, with pacing ΓòÉΓòÉΓòÉ This example shows a positive response trace. <==SEND===== SDLC #00 00000714C3AA3564 14:16:21:00 #:0009 TH:2C0001060013 RH:838100 The RH indicates RQD1, with the pacing indicator on. This frame corresponds with a previous received frame that should have the same TH field (except bytes 3 and 4, the OAF and DAF, are swapped). In the RH field, the 1 in the second half of the second byte is the pacing indicator. ΓòÉΓòÉΓòÉ 4.3.2.1.13. RH:83A000, CONFIRMED verb issued ΓòÉΓòÉΓòÉ This example shows a trace with the CONFIRMED verb issued. The RH indicates RQD3, with a positive response. <==SEND===== SDLC #00 0000E70E053C646B 13:01:37:00 #:0009 TH:2E000107802F RH:83A000 ΓòÉΓòÉΓòÉ 4.3.2.1.14. RH:879000, Reject of an FM Header ΓòÉΓòÉΓòÉ This example shows an FM Header trace. This is a reject of an attach. <==SEND===== SDLC #00 0000E70E053C646B 13:03:17:84 #:000D TH:2E000106802E RH:879000 08460000 <.F.. > Field Description RH: 879000 This field is the RH for this PIU. 08460000 Sense data. This field indicates: "The received request was rejected for a reason to be specified in a forthcoming request". To determine the exact reason the request was rejected, look at the sense data in the next RU. This information is also in the Communications Manager error log. The sense data is in an FMH-7, as shown in this example: <==SEND===== SDLC #00 0000E70E053C646B 13:03:18:25 #:0010 TH:2E0001060009 RH:0A9100 07070889 000000 <...i... > The following example contains sense data associated with the reject. Field Description 07 This field is the length of the FM header, in hexadecimal format. 07 This field is an FM header type 7 (FMH-7). 08890000 Sense data. ΓòÉΓòÉΓòÉ 4.3.2.1.15. RH:CB8000, RTS response ΓòÉΓòÉΓòÉ This example shows a response to a Request_to_send trace. APPC sends this response to the previous incoming Request_to_send signal. <==SEND===== SDLC #00 0000E70E053C646B 13:01:38:15 #:000A TH:2F000103803A RH:CB8000 C9 <I > ΓòÉΓòÉΓòÉ 4.3.2.2. DFT DLC Trace ΓòÉΓòÉΓòÉ You can enable the DFT DLC trace using any of the following methods: o Selecting DFTDLC from the DLC column of the Problem Determination Aids - Trace Services window o Using the CMTRACE command o Specifying the dft_dlc parameter of the DEFINE_TRACE common services verb The DFT DLC trace is a trace of all DFT DLC data sent and received. The request/response unit (RU) header data is truncated to the length of the trace record. Note: If swapping occurs during a trace, controller errors may result. To prevent swapping, make sure that the workstation has sufficient memory for the trace operation. The following is an example of a DFT DLC trace: DFTDLC 15:48:02.43 OUTB: [LH:] l=19 (0013) 0000 [TH:] OIS 98->98 SNF=0001 [RH:] REQ FMD OIC DR1I PI BBI CDI [RU:] 3..... f000f0 3051f2 DFTDLC 15:48:02.43 POLL: SS=FCIR(00) DFTDLC 15:48:02.46 STARTOP: F=RDAT(00,04,01,00),lt=98 DFTDLC 15:48:02.46 INB: [LH:] l=13 (000d) c000 [TH:] OIS 98<-98 SNF=0001 [RH:] +RSP FMD OIC DR1I PI The DFT DLC postprocessor produces this format: o Header line This header line contains the trace type (DFTDLC) and a time stamp of when the trace began. o SNA inbound data is displayed in the trace as follows: INB: [LH:] l=lxxx (lyyy) lzzz [TH:] txx tyy<-tzz tww SNF=tsss [RH:] r c f cf d1 d2 e q p bb cs [RU:] sd rc ascii data hex data Length header (LH) data is as follows: lxxx Length in decimal lyyy Length in hex lzzz Flags in hex Transmission header (TH) data is as follows: txx Segment field type: FIS First in segment OIS Only in segment MIS Middle in segment LIS Last in segment tyy Destination address field (DAF) in decimal tzz Origin address field (OAF) in decimal tww Expedited flow indicator (EFI) or nothing tsss Sequence number field in hexadecimal Request header (RH) data is displayed if transmission header flag bit 0x08 (begin basic information unit) is on. RH data is as follows: r Request (REQ) or response (RSP) type (+/-) c RH category: FMD Function management data NC Network control DFC Data flow control SC Session control f Format indicator (FI) cf Chain flags: FIC First in chain OIC Only in chain MIC Middle in chain LIC Last in chain The following fields are not always displayed: d1 Definite response 1 indicator (DR1I) d2 Definite response 2 indicator (DR2I) e Exception response indicator (ERI) q Queued response indicator (QRI) p Pacing indicator (PI) bb Bracket indicator: BBI Begin bracket indicator EBI End bracket indicator CDI Change direction indicator cs Data indicators: CSI Code selection indicator EDI Enciphered data indicator PDI Padded data indicator If any RU data is present, it is displayed next. RU data is as follows: sd SD=dddd (sense data in hex if present) rc Request code if present ASCII data EBCDIC contents of the rest of the RU, up to the length of data traced, formatted into ASCII Hex data EBCDIC contents of the rest of the RU, up to the length of data traced, formatted into hex o SNA outbound data The format of the SNA outbound data is the same as the inbound data, except that the leading tag is OUTB. o Non-SNA inbound data The fields that follow the LH are displayed only if LH is displayed in the entry. The data is represented in character form with its EBCDIC hex value below each character. For example: INB: cmd xcmd ydata attn flgs LH l=ddd bbbb MFa MFb DATA: ABC10 CCCFF 12301 The abbreviations used in this example of non-SNA inbound data (INB) are defined as follows: cmd 3270 data stream command: EWRT Erase/write EWRA Erase/write alternate WRT Write EAU Erase all unprotected WSF Write structured field RDBF Read buffer RDMD Read modified RDMA Read modified all xcmd Command chaining: Bcmd Begin chain Ccmd Complete chain Icmd In chain Ecmd End chain ydata Data chaining: Bdata Begin chain Cdata Complete chain Idata In chain Edata End chain attn AttnAck (last attention/AID accepted) or nothing flgs Flags for command, data chaining, and AttnAck ddd Length of message segment in decimal bbbb Length of message segment in hex MFa MFaFLAGS, first flag byte in message, in hex MFb MFbFLAGS, second flag byte in message, in hex o Non-SNA outbound data The format of the non-SNA outbound data is the same as the format of the inbound data, except that the leading tag is OUTB. o STARTOP These are start operations sent from the 3x74 control unit to your workstation. The mnemonic for the function-request value is followed by the four function request parameters and the logical terminal address. The following is an example of a STARTOP entry: STARTOP: F=CUFRV(p1,p2,p3,p4),lt=nn where CUFRV is the control unit function request value, p1, p2, p3, and p4 are request parameters, and lt has the variable value nn. The CUFRV value can be any one of the following: CNOP No operation WCUS Write control unit status WDAT Write data from host WLCC Write channel command LOCK Non-SNA host selection RDAT Generate read data for host PDAT Prepare data for future read CTCCS Terminate chained cmd sequence UNDEF Undefined value o POLL The following are the synchronous (SS=DSSV), asynchronous (AS=DAEV), and expedited ( ES=EXFRQ) statuses that 3270 terminal emulation sends to the 3x74 control unit. The mnemonic for the status value is placed after the equal sign (=). Should there be more than one type of status posted to the 3x74 control unit at once, the synchronous status is displayed first, followed by the asynchronous status and the expedited status. The first status parameter is output with SS and AS status. The logical terminal address (lt=nn) is output with AS and ES status. Synchronous Status POLL: SS=DSSV(p1) Value DSSV Synchronous status X'02' FCSE = function complete with synchronous error X'04' FC = function complete X'06' FCIR = function complete with input required X'08' ERFR = error in function request X'0A' FRA = function request aborted X'0C' FCDEF = function complete deferred X'xx' UNDEF = undefined value synchronous status parameters DSSP1 Synchronous status parameter 1 X'01' device busy (FCSE status) X'02' device error (FCSE status) X'03' command reject (FCSE status) X'04' intervention req'd (FCSE status) X'05' data check (FCSE status) X'06' op check (FCSE status) X'00' RDAT required (FCIR status) X'01' data available in (FCIR status) buffer X'00' unsupported protocol (ERFR status) X'01' unsupported CUFRV (ERFR status) X'02' unsupported parameter (ERFR status) X'03' unsupported offset (ERFR status) X'04' CUSYN synch. error (ERFR status) X'06' outbound data flag err(ERFR status) X'07' CULTAD not valid or (ERFR status) undefined X'08' func request data err (ERFR status) X'10' device (ERFR status) | . ( | ) | specific ( | ) V . ( V ) X'FF' errors (ERFR status) X'FE' default printer (for AEPID) X'xx' anything else = operator printer assignment (for AEPID) Asynchronous Status POLL: AS=DAEV(p1),lt=nn Value DAEV Asynchronous status X'22' AEEP = inbound event pending X'28' AEDV = device / cu status control X'34' AESTAT = asynchronous response to start operation X'xx' UNDEF = undefined value DAEP1 Asynchronous parameter 1 X'01' ONLINE = online param (AEDV) X'02' OFFLINE = offline param (AEDV) Expedited Status POLL: ES=EXFRQ,lt=nn Value EXFRQ Expedited status X'02' BUSY = device still busy X'xx' UNDEF = undefined value o CU_DISCONNECT This is a trace of the error code sent by the 3x74 control unit after disconnecting. The halfword error code sent is traced. CU disconnect: CUDSER=nnnn CUDSER Halfword 3x74 Control Unit error code o Power-on Reset This trace is an indication that 3270 terminal emulation is about to send a power-on reset to the 3x74 control unit. This usually occurs after a disconnect has been received from the 3x74 control unit. This also occurs at the start of a trace if tracing is started before 3270 terminal emulation for DFT is started. This can also occur when a power-on reset is performed. No other data is displayed in this trace entry. o READID This trace is an indication that the 3x74 control unit has received an expedited status and has responded to the workstation. No other data is displayed in this trace entry. o (Duplicate STARTOP) This trace is an indication that the workstation has received a STARTOP trace command from the 3x74 control unit, but that the CUSYN value has not switched. No other data is displayed in this trace entry. o RESET This trace is an indication that a reset or diagnostic reset has been read from the adapter status register. No other data is displayed in this trace entry. o IDENT IDENT traces the data sent by the device to the 3x74 control unit at power-on reset to identify the device. It is also used when the data is sent by the 3x74 control unit to the device that identifies the control unit. For example: IDENT: ACS3 CCEF 1323 The data is represented in character form with its EBCDIC hex value below each character. o PACE denied This trace is an indication that no buffers are available for the API data. o AID: xx [z] This traces the sending of an attention identifier (AID) key on a non-SNA link. The code xx is the hexadecimal code for the AID key, and z is a decimal number that identifies the logical terminal. o UNKNOWN This traces an unrecognized trace event type. It takes the following form, where yyyyy is the length of the trace entry, zz is the trace event type (in hex), and xx xx xx ... is the trace data displayed as hex bytes. UNKNOWN: l=yyyyy t=zz xx xx xx xx xx xx xx xx ... ΓòÉΓòÉΓòÉ 4.3.2.3. ETHERAND DLC Trace ΓòÉΓòÉΓòÉ You can enable the ETHERAND DLC trace using any of the following methods: o Selecting ETHERAND from the DLC column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the PC Network parameter of the DEFINE_TRACE common services verb Both the send and the receive data are traced. The first header lines contain the following: o Send header line: <=SEND=== ETHERAND adapter# adapter address link ID time stamp o Receive header line: =RECV===> ETHERAND adapter# adapter address link ID time stamp The second header contains the following in hexadecimal format: #:RU_size TH:transmission header RH:request-response header2 The ETHERAND DLC trace contains the data listed in the following table. Data in the ETHERAND DLC Trace Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 Variable (may RU be truncated) Refer to Systems Network Architecture Network Product Formats for information on formatting individual RUs. The following is an example of an ETHERAND DLC trace: <==SEND===== ETHERAND #00 400000000002 604E3F194EF4746F 10:16:04:50 #:1200 TH:2D0000000000 RH:6B8000 11020104 00000000 00 <......... > ===RECV====> ETHERAND #00 400000000002 604E3F194EF4746F 10:16:04:53 #:1300 TH:2D0000000000 RH:EB8000 11024040 40404040 4040 <.. > <==SEND===== ETHERAND #00 400000000002 604E3F194EF4746F 10:16:04:53 #:0C00 TH:2D0000000000 RH:6B8000 0D0201 < > ===RECV====> ETHERAND #00 400000000002 604E3F194EF4746F 10:16:04:78 #:1900 TH:2D0000000000 RH:6B8000 0D010100 85000000 0C060300 01000000 <....e...........> ΓòÉΓòÉΓòÉ 4.3.2.4. IBM PC Network DLC Trace ΓòÉΓòÉΓòÉ You can enable the IBM PC Network DLC trace using any of the following methods: o Selecting IBMPCNET from the DLC column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the ibmpcnet_data parameter of the DEFINE_TRACE common services verb Both the send and the receive data are traced. The first header lines contain the following: o Send header line: <=SEND=== IBMPCNET adapter# adapter address link ID time stamp o Receive header line: =RECV===> IBMPCNET adapter# adapter address link ID time stamp The second header contains the following in hexadecimal format: #:RU_size TH:transmission header RH:request-response_header The IBM PC Network DLC trace contains the data listed in the following table. Data in the IBM PC Network DLC Trace Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 Variable (may RU be truncated) Refer to Systems Network Architecture Network Product Formats for information on formatting individual RUs. The following is an example of an IBM PC Network DLC trace: <==SEND===== IBMPCNET #01 400000000018 00007742331BF76B 15:35:29:78 #:5700 TH:2D0001011B35 RH:6B8000 31001307 B0B0D0B1 08008585 80080602 <1.........ee....> 00000000 00000000 20000008 D5C5E3F1 <........ ...NET1> 4BD3E4F1 1F000902 D4D6C4C5 F1404040 <KLU1....MODE1 > 0903001B F76B361B F76B0904 D5C5E3F1 <....7k6.7k..NET1> 4BD3E4F1 0008D5C5 E3F14BD3 E4F2 <KLU1..NET1KLU2 > ===RECV====> IBMPCNET #01 400000000018 00007742331BF76B 15:35:29:84 #:4600 TH:2D0001011B35 RH:EB8000 31001307 B0B0D0B1 08088585 88080602 <1.........eeh...> 00000000 00000000 20000000 1F000902 <........ .......> D4D6C4C5 F1404040 0903001B F76B361B <MODE1 ....7k6.> F76B0905 D5C5E3F1 4BD3E4F2 00 <7k..NET1KLU2. > ΓòÉΓòÉΓòÉ 4.3.2.5. IBM Token-Ring DLC Trace ΓòÉΓòÉΓòÉ You can enable the IBM Token-Ring DLC trace using any of the following methods: o Selecting IBMTRNET from the DLC column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the ibmtrnet_data parameter of the DEFINE_TRACE common services verb Both the send and the receive data are traced. The first header lines contain the following: - Send header line: <=SEND=== IBMTRNET adapter# adapter address link ID time stamp - Receive header line: =RECV===> IBMTRNET adapter# adapter address link ID time stamp The second header contains the following in hexadecimal format: #:RU_size TH:transmission header RH:request-response header The IBM Token-Ring DLC trace contains the data listed in the following table. Data in the IBM Token-Ring DLC Trace Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 Variable (may RU be truncated) Refer to Systems Network Architecture Network Product Formats for information on formatting individual RUs. The following is an example of an IBM Token-Ring DLC trace: <==SEND===== IBMTRNET #00 400000000008 00008F43758BEF6B 14:17:09:62 #:8400 TH:2C0001010002 RH:0B9020 130502FF 0003D100 4008C6C9 D3C5D4E2 <......J...FILEMS> E5D90000 6812FF03 65000000 000000E2 <VR..h...e......S> 1F1E2B00 E400002C 1F1E2B00 E4000030 <..+.U..,..+.U..0> 241E2B00 E4000000 00000000 000000D1 <$.+.U..........J> 1E1E2B00 E4000065 1D1E2B00 E400001B <..+.U..e..+.U...> 1E1E2B00 E4000000 00000000 0000009E <..+.U...........> 1B1E2B00 E4000075 351E2B00 E4000071 <..+.U..u5.+.U..q> 221E2B00 E4000000 000000 <".+.U...... > ===RECV====> IBMTRNET #00 400000000008 00008F43758BEF6B 14:17:09:84 #:0901 TH:2C0001010002 RH:029000 100412FF 01000010 01010043 46470200 <...........CFG..> 000E0000 007A0300 0300008C 03008039 <.....z.........9> 00000400 00C60300 1D050000 05000002 <.....F..........> 00000100 00100101 00434647 0200000E <.........CFG....> 0000007A 03000300 008C0300 80390000 <...z.........9..> 040000C6 03001D05 00000500 00020000 <...F............> 01000010 01010043 46470200 000E0000 <.......CFG......> 007A0300 0300008C 03008039 00000400 <.z.........9....> 00C60300 1D050000 05000002 00000100 <.F..............> 00100101 00434647 0200000E 0000007A <.....CFG.......z> 03000300 008C0300 80390000 040000C6 <.........9.....F> 03001D05 00000500 00020000 01000010 <................> 01010043 46470200 000E0000 007A0300 <...CFG.......z..> 0300008C 03008039 00000400 00C60300 <.......9.....F..> 1D050000 05000002 00000100 00100101 <................> 00434647 0200000E 0000007A 03000300 <.CFG.......z....> ΓòÉΓòÉΓòÉ 4.3.2.6. SDLC DLC Trace ΓòÉΓòÉΓòÉ You can enable the Synchronous Data Link Control (SDLC) DLC trace using any of the following methods: o Selecting SDLC from the DLC column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the sdlc_data parameter of the DEFINE_TRACE common services verb Both the send data and the receive data are traced. The first header lines contain the following: o Send header line: <==SEND===== SDLC adapter# link ID time stamp o Receive header line: ===RECV====> SDLC adapter# link ID time stamp The second header contains the following in hexadecimal format: #:RU_size TH:transmission header RH:request-response header The SDLC DLC trace contains the data listed in the following table. Data in the SDLC DLC Trace Offset Length Description ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 0 Variable (may RU be truncated) Refer to Systems Network Architecture Network Product Formats for information on formatting individual RUs. The following is an example of an SDLC DLC trace: ===RECV====> SDLC #00 0000F70F423487B5 11:49:40:15 #:0900 TH:2C0001010000 RH:830100 <==SEND===== SDLC #00 0000F70F423487B5 11:49:40:90 #:0A00 TH:2C0001010003 RH:4B8000 70 ΓòÉΓòÉΓòÉ 4.3.2.7. X.25 DLC Trace ΓòÉΓòÉΓòÉ You can enable the X.25 DLC trace using any of the following methods: o Selecting X25_DLC from the DLC column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the x25_dlc_data parameter of the DEFINE_TRACE common services verb Both the send and the receive data are traced. The first header lines contain the following fields: o Send header line: <==SEND===== X25DLC adapter# adapter address link ID time stamp o Receive header line: ===RECV====> X25DLC adapter# adapter address link ID time stamp The second header contains the following in hexadecimal format: #RU_size TH:transmission header RH:request-response header The following is an example of an X.25 DLC DLC trace: ===RECV====> X25DLC #00 FF0001 90364F1D24ED014E 11:25:43:28 #:6000 TH:2D000102EF6E RH:6B8000 31001307 B0B0D0B1 08008787 80080602 <1.........gg....> 00000000 00000000 2000000B E2E5E34B <........ ...SVTK> D3E4E2C5 D5C4F122 000902D4 D6C4C5F1 <LUSEND1"...MODE1> 40404009 0300EF01 4E6FEF01 4E0C04E2 < .....No..N..S> E5E34BD3 E4E2C5D5 C4F1000B E2E5E34B <VTKLUSEND1..SVTK> D3E4D9C5 C3E5F1 <LURECV1 > <==SEND===== X25DLC #00 FF0001 90364F1D24ED014E 11:25:43:28 #:4900 TH:2D000201EF6E RH:EB8000 31001307 B0B0D0B1 08088787 88080602 <1.........ggh...> 00000000 00000000 20000000 22000902 <........ ..."...> D4D6C4C5 F1404040 0903F0EF 014E6FEF <MODE1 ..0..No.> 014E0C05 E2E5E34B D3E4D9C5 C3E5F100 <.N..SVTKLURECV1.> ===RECV====> X25DLC #00 FF0001 90364F1D24ED014E 11:25:43:50 #:1C00 TH:2C0001020001 RH:0BA100 130502FF 0003D100 4008E3D7 E2C5D9E5 <......J. .TPSERV> C5D900 <ER. > <==SEND===== X25DLC #00 FF0001 90364F1D24ED014E 11:25:43:50 #:0900 TH:2C0002010000 RH:830100 <==SEND===== X25DLC #00 FF0001 90364F1D24ED014E 11:25:53:15 #:0900 TH:2C0002018000 RH:83A000 ===RECV====> X25DLC #00 FF0001 90364F1D24ED014E 11:25:54:12 #:4C00 TH:2C0001020002 RH:03A000 004312FF 4A696D4B 39433A5C 524A5052 <.C..JimK9C:\RJPR> 4F475C52 43535043 4441542E 5453382C <OG\RCSPCDAT.TS8,> 433A5C72 6A70726F 675C5243 5646494C <C:\rjprog\RCVFIL> 45535C52 43535043 4441542E 434D3100 <ES\RCSPCDAT.CM1.> 000000 <... > <==SEND===== X25DLC #00 FF0001 90364F1D24ED014E 11:25:55:40 #:0900 TH:2C0002018000 RH:83A000 ===RECV====> X25DLC #00 FF0001 90364F1D24ED014E 11:25:59:53 #:1300 TH:2C0001020003 RH:03A000 000A12FF 31303936 3600 <....10966. > <==SEND===== X25DLC #00 FF0001 90364F1D24ED014E 11:26:00:12 #:0900 TH:2C0002018000 RH:83A000 ΓòÉΓòÉΓòÉ 4.3.2.8. X.25 Frame DLC Trace ΓòÉΓòÉΓòÉ The X.25 frame DLC trace allows you to trace the frame-level data being handled by the X.25 API. You can enable the X.25 frame DLC trace using any of the following methods: o Selecting X25_API FRAME from the DLC column of the Problem Determination Aids - Trace Services window. o Using the CMTRACE command o Specifying the x25_api_frame_data parameter of the DEFINE_TRACE common services verb Send, receive, and control data are traced. The first header line contains the following: o Send header line: <==SEND===== X25API Process ID Link Link ID time stamp Thread ID o Receive header line: ===RECV====> X25API Process ID Link Link ID time stamp Thread ID The time stamp indicates: hours:minutes:seconds:centiseconds (00:00:00:00) Note: The time stamp is placed on each record by the X.25 DLL. The events actually occur on the X.25 Interface Co-Processor adapter. Synchronization of event timing between the X.25 Interface Co-Processor and the X.25 DLL is not guaranteed. The following is an example of an X.25 frame trace. It shows the call packet, the call confirm packet, and the data send packet. <==SEND===== X25API 0011/0005 Link LINK1 O9:59:06:62 PS 0 0107 CALL dY la:15 lf:0 ld:0 FF222222 22222222 21111111 11111111 <."""""""!.......> 00 <. > <==SEND===== X25API 0011/0005 Link LINK1 O9:59:06:96 FS 0 INFO 1 0 5 5 51070BFF 22222222 22222221 11111111 <Q..."""""""!....> 11111100 <.... > ===RECV====> X25API 0011/0005 Link LINK1 O9:59:07:09 FR 0 RR 1 0 6 ===RECV====> X25API 0011/0005 Link LINK1 O9:59:07:75 FR O INFO 3 0 6 5 51070FFF 22222222 22222221 11111111 <Q..."""""""!....> 11111100 <.... > ===RECV====> X25API 0011/0005 Link LINK1 O9:59:08:06 PR O O107 CF CALL dY la:15 lf:0 ld:0 FF222222 22222222 21111111 11111111 <."""""""!.......> 00 <. > <==SEND===== X25API 0011/0005 Link LINK1 O9:59:08:34 FS 0 RR 3 0 6 <==SEND===== X25API 0011/0005 Link LINK1 O9:59:15:62 PS 0 0107 DATA pr:0 ps:0 dN mY qN 1:128 68656C6C 6F202020 20202020 20202020 <hello > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > 20202020 20202020 20202020 20202020 < > The following is an example of a line control event: CONTROL X25API 0013/005 Link LINK1 15:43:27:65 FC 0 LEV1 DOWN X.25 Frame Tracing Formats X.25 frame tracing operates on two levels: o The frame level o The packet level The following sections discuss the format of each of these levels. Frame level display format An X.25 frame level trace has the following format: FX N NAME ADDR P/F NR NS DATA The characters in this format are defined as follows: F Identifies a frame level trace, and the character X is: R Signals that a frame has been received on the link. S Signals that a frame has been sent on the link. C For all events related to the line control. These are the level 1 or 2 connection and disconnection traces and the loss of carrier messages. A To signal that a frame has been sent on the link but has been aborted. N Is always 0. NAME The name of the frame sent or received (or of the line control trace). ADDR The address field of the frame. P/F The value of the poll/final bit. The remaining fields are present only for information frames: NR The value of the frame receive sequence number N(R). NS The frame send sequence number N(S). DATA The data field for an information frame. The data field, when enabled, is always displayed in hex (4 bytes are always displayed). The following is a list of all the valid frame codes for NAME when X = R or S: RR RR frames RNR RNR frames REJ REJ frames SABM SABM frames DM DM frames DISC DISC frames UA UA frames FRMR FRMR frames ERROR ERROR frames INFO Information frames BACK Bad acknowledgment; N(R) is incorrect UNK Unknown frame SIZE Length error DUST Information frames discarded because of a shortage of buffers ABORTED Received frame was discarded at the sending end IGN Frame was ignored The following is a list of valid codes where X = C: LEV1 UP Level 1 connected LEV1 DOWN Level 1 disconnected LEV2 UP Level 2 connected LEV2 DOWN Level 2 disconnected CARRIER Level 1 CD change The following is the valid code when X = A: INFO Information frame Packet level display format An X.25 packet level trace has the following format: PX N VC NAME packet_data The characters in this format are defined as follows: P Identifies a packet level diagnostic, and the character X is: R Signals that a packet has been received on the link. S Signals that a packet has been sent on the link. N Is always 0. VC The virtual circuit number (in hexadecimal digits). NAME The name of the packet sent or received (or of the line control trace). The remaining fields depend upon the packet type and include the following: o The value of the m, q, and d; for example, dY, mN, where Y=yes, N=no o The length of the address (a) and facility (f) fields associated with call processing packets (for example, la:15, lf:o) o The length of the data field associated with call processing packets; for example, ld:128 o The values of the P(s) and P(r) fields o The size of data packets; for example, l:128 The following is a list of valid codes when X = R or S: DATA DATA packets RR RR packets RNR RNR packets CALL CALL packets CF CALL CALL CONFIRM packets CLEAR CLEAR packets CF CLEAR CLEAR CONFIRM packets INTER INTERRUPT packets CF INTER INTERRUPT CONFIRM packets RESET RESET packets CF RESET RESET CONFIRM packets DIAG DIAGNOSTIC packets RESTART RESTART packets CF REST RESTART CONFIRM packets ERROR Unrecognized packets The following is a list of valid codes when X = C: CONNECT Packet level connected DISC Packet level disconnected ΓòÉΓòÉΓòÉ 4.4. Formatted Traces ΓòÉΓòÉΓòÉ This section contains examples of formatted traces that are supported by Communications Manager. You can use Problem Determination Aids - Trace Services or the FMTTRACE command to format certain Communications Manager trace files into an easier-to-read form. You can format trace records for the APPC API, APPC send events, and DLC data. You can produce two types of formatted output: a summary file (in sequence diagram form with one line per trace event), and a detail file (with one line per formatted field). The following example shows a single data send event in a trace of the DLC data. <==SEND===== IBMPCNET #00 50000000004404 0000D742FC8F9161 11:02:49:09 #:006F TH:2F0001018FFE RH:6B8000 31001307 B0B0D0B1 08008787 80080602 <1.........gg....> 00000000 00000000 23000010 E3D9D5D5 <........#...TRNN> C5E3F0F1 4BD3E4F4 F3C3F0F1 27000902 <ET01KLU43C01'...> E2D5C1E2 E5C3D4C7 0903008F 9161FF8F <SNASVCMG....ja..> 91611104 E3D9D5D5 C5E3F0F1 4BD3E4F4 <ja..TRNNET01KLU4> F3C3F0F1 0010E3D9 D5D5C5E3 F0F14BD3 <3C01..TRNNET01KL> E4F4F4C3 F0F1 <U44C01 > Assuming the preceding trace record was the only contents of file X.Y, the following was entered at the command line to obtain detailed information about this trace entry: FMTTRACE -D X.Y The following example of the detailed output for this trace record was formatted using this FMTTRACE command. Notice that the 9 lines in the trace file expanded to about 75 lines of detailed output. FMTTRACE (C) Copyright IBM Corporation 1990, 1991 Line: 1 Send MU Time stamp: 11:02:49:09 DLC type: IBMPCNET Adapter number: 00 Destination address: 50000000004404 ALS ID: 0000D742FC8F9161 TH: FID2, Exp, OIS, LFSID=0x10101, SNF=0x8ffe RH: RQ, SC, FI, OIC, RQD1 BIND rq Type = Negotiable FM profile = 19 TS profile = 7 FM usage - primary: Chaining use = Multiple-RU chains allowed Request control mode = Immediate request mode Chain response protocol = Definite or exception response Two-phase commit = Not supported Compression = Will not be used Send end bracket = Will not send FM usage - secondary: Chaining use = Multiple-RU chains allowed Request control mode = Immediate request mode Chain response protocol = Definite or exception response Two-phase commit = Not supported Compression = Will not be used Send end bracket = Will not send FM Usage - common: Whole BIUs required = Yes FM header usage = Allowed Bracket usage and reset state = Brackets are used and reset state is INB Alternate code set allowed = No BIND queueing allowed = No Normal-flow send/receive mode = Half-duplex flip-flop Recovery responsibility = Symmetric Contention winner = Primary Alternate code set = ASCII-7 Control vectors included = No Half-duplex flip-flop primary reset state = Send TS usage: Secondary to primary pacing stages = One Secondary send window size = 8 Adaptive pacing = Not supported Secondary receive window size = 0 Secondary maximum send RU size = 1024 Primary maximum send RU size = 1024 Primary to secondary pacing stages = One Primary send window size = 0 Primary receive window size = 8 PS profile: LU type = 6 LU-6 level = 2 Conversation-level security = Accepted Already-verified indicator = Not accepted Synchronization level supported = Confirm Session reinitiation responsibility = Operator controlled Parallel sessions supported = Yes CNOS supported = Yes Limited resource = No Cryptography options: Private cryptography support = No Session-level cryptography support = No Primary LU name = TRNNET01.LU43C01 Structured user data: Mode name = SNASVCMG Session instance identifier = 0x008f9161ff8f9161 Network-qualified PLU name = TRNNET01.LU43C01 Secondary LU name = TRNNET01.LU44C01 ΓòÉΓòÉΓòÉ 5. Diagnostic Tools ΓòÉΓòÉΓòÉ In addition to FFST/2 and the Trace and Dump Services, Communications Manager provides you with the following tools for problem determination: CMPD CMQUERY CMRECORD Common Services Application Programming Interface Communications Manager Subsystem Management DISPLAY PMDSPLAY PSTAT QSYSTEM ΓòÉΓòÉΓòÉ 5.1. CMPD ΓòÉΓòÉΓòÉ CMPD is a utility that automatically collects certain files which can be used for problem determination. Once collected, CMPD compresses these files to save space. You can send these files to your local support personnel or to IBM Service to aid in problem determination. Use the following syntax for CMPD: CMPD pmr_number drive1 drive2 where: pmr_number is any 8-character string. Note: If you have already contacted IBM, you may have been assigned a PMR number. If so, use that number; otherwise you can use any 8-character string you choose. drive1 is the drive where Communications Manager is installed. drive2 is the drive where NTS/2 is installed (optional). CMPD searches for and collects the following files: o CONFIG.SYS o All Communications Manager configuration files (*.CFG, *.CF2, *.NDF, and *.SEC) o \CMLIB\CM.LOG (the installation audit trail log) o \CMLIB\CMRINST.LOG (the remote installation log) o \CMLIB\UPGRADE.LOG o \CMLIB\VERIFY.LOG o \IBMCOM\PROTOCOL.INI (if you are using NTS/2) o \IBMCOM\LANTRAN.LOG (if you are using NTS/2) o \OS2\SYSTEM\LOG0001.DAT (the system error log) o \OS2\SYSTEM\LOG0001.BAK (the system error log backup) o \OS2\SYSTEM\OS2MLOG.DAT (the default FFST/2 message log) o \OS2\SYSTEM\*.DMP (the FFST/2 dump files) CMPD also executes the following commands and captures the output: o CMQUERY > CMQUERY.TXT o DISPLAY > DISPLAY.TXT o PSTAT > PSTAT.TXT o QSYSTEM > QSYSTEM.TXT CMPD also searches for pmr_number*.* to gather any files which may be associated with your PMR. CMPD uses SAVERAM to compress all the files it finds into a file named \CMLIB\pmr_number.RAM (where pmr_number is the 8-character string you supplied). CMPD also keeps a log of the files it collects and displays this log on your screen. ΓòÉΓòÉΓòÉ 5.2. CMQUERY ΓòÉΓòÉΓòÉ CMQUERY is a sample program that provides command line status information about Communications Manager and Communications Manager configurations. Refer to Command Reference for additional information. ΓòÉΓòÉΓòÉ 5.3. CMRECORD ΓòÉΓòÉΓòÉ CMRECORD can be used to create an ASCII representation of your Communications Manager configuration. This file is called a response file. Although it is used primarily during remote configuration of Communications Manager, CMRECORD can also be used for problem determination. You can review the response file and compare your configuration with other configurations. Refer to Command Reference for additional information. ΓòÉΓòÉΓòÉ 5.4. Common Services Application Programming Interface ΓòÉΓòÉΓòÉ Common Services is an application programming interface (API) provided by Communications Manager. This API provides service verbs which all application programs can use to assist with such functions as ASCII-to-EBCDIC conversion, tracing of API interfaces and data, logging of messages in the FFST/2 message log, retrieval of system errors and messages, and transfer of diagnostic information to a host computer. For more information on the Communications Manager service verbs, refer to Application Programming Guide. ΓòÉΓòÉΓòÉ 5.5. Communications Manager Subsystem Management ΓòÉΓòÉΓòÉ Communications Manager subsystem management is an online facility for monitoring and controlling communications resources maintained by Communications Manager. It is used by individuals performing installation, testing, tuning, and special development activities of SNA Communication Services. It can also be used to assist during problem determination. For example, you can use subsystem management to display the status of a transaction program with which you are having problems. If you determine that the program is not functioning as you expect, you can use subsystem management to deactivate the program so that it can be restarted or modified. You can access subsystem management by selecting Communications Manager/2 from the desktop and then selecting Subsystem Management. Note: The Communications Manager kernel must be started before other services can be started. You can perform the following tasks from the Subsystem Management window: o Start or stop APPC attach manager o Start or stop the Communications Manager kernel o Start or stop the SNA subsystem o Display X.25 physical link information o Display SNA X.25 virtual circuit information Note: The status of ACDI and SRPI is displayed on the Subsystem Management window. No further information about these components is available. For more information about subsystem management, refer to Planning and Administration for Networks. ΓòÉΓòÉΓòÉ 5.5.1. APPC Attach Manager ΓòÉΓòÉΓòÉ To start or stop APPC attach manager from the Subsystem Management window, do the following: 1. Select APPC attach manager from the list. 2. Select Service from the menu bar. 3. Select either Start or one of the stop options. ΓòÉΓòÉΓòÉ 5.5.2. Communications Manager Kernel ΓòÉΓòÉΓòÉ To start or stop the Communications Manager kernel from the Subsystem Management window, do the following: 1. Select Communications Manager kernel from the list. 2. Select Service from the menu bar. 3. Select either Start or one of the stop options. ΓòÉΓòÉΓòÉ 5.5.3. SNA Subsystem ΓòÉΓòÉΓòÉ To start or stop the SNA subsystem from the Subsystem Management window, do the following: You can also display more information about the configuration. 1. Select SNA subsystem from the list. 2. Select Service from the menu bar. 3. Select either Start or one of the stop options, or select Details. If you select Details, the SNA Subsystem window is displayed. From this window, you can perform the following tasks: o Deactivate active transaction programs o Display - Adapter information - APPN class of service information - APPN connection networks - APPN directory - APPN intermediate sessions - APPN nodes - APPN topology - Currently active transaction programs - Global SNA information - Incoming call answer status - Link definitions - Link information - Logical units 0 to 3 - Logical units 6.2 - LU definitions - LU 6.2 sessions - Management services - Mode definitions - Partner LU definitions - Physical units - Signed-on users - SNA gateway information - System defaults - Transaction program definitions - Transaction programs - X.25 physical links o Establish LU 6.2 sessions o Change limits of LU 6.2 sessions o Deactivate active LU 6.2 sessions o Activate logical links o Deactivate active logical links (normal and abnormal) o Activate data link controls o Deactivate data link controls o Answer incoming calls o Reject incoming calls ΓòÉΓòÉΓòÉ 5.5.4. X.25 Physical Link Information ΓòÉΓòÉΓòÉ To display X.25 physical link information from the Subsystem Management window, do the following: 1. Select X.25 physical links from the list. 2. Select Service from the menu bar. 3. Select Details. The X.25 Physical Links window is displayed. From this window, you can perform the following tasks: o Display X.25 physical link information o Place an X.25 physical link in connect mode o Place an X.25 physical link in autoconnect mode o Place an X.25 physical link in disconnect mode ΓòÉΓòÉΓòÉ 5.5.5. SNA Virtual Circuit Information ΓòÉΓòÉΓòÉ To display SNA X.25 virtual circuit information from the Subsystem Management window, do the following: 1. Select SNA X.25 virtual circuits from the list 2. Select Service from the menu bar 3. Select Details The SNA X.25 Virtual Circuits window is displayed. From this window, you can perform the following tasks: o Display SNA X.25 virtual circuit information o Deactivate SNA X.25 virtual circuits ΓòÉΓòÉΓòÉ 5.6. DISPLAY ΓòÉΓòÉΓòÉ DISPLAY allows you to display status and configuration information for an active SNA configuration from the OS/2 command line. Refer to Command Reference for additional information. ΓòÉΓòÉΓòÉ 5.7. PMDSPLAY ΓòÉΓòÉΓòÉ PMDSPLAY allows you to display status and configuration information for an active SNA configuration by using Presentation Manager windows. Refer to Command Reference for additional information. ΓòÉΓòÉΓòÉ 5.8. PSTAT ΓòÉΓòÉΓòÉ PSTAT is an OS/2 utility that returns process status information about which threads are running in the system, along with their current status and current priorities. PSTAT displays the process ID that is assigned for tracing on a per-process basis and is used to get global system information. PSTAT can assist you in determining: o Why a given thread is hung (stopped, waiting on system event) o Why the performance of the thread is sluggish (relatively low priority compared to other threads) To use the PSTAT utility, type PSTAT on the OS/2 command line. For more information on the PSTAT utility, refer to OS/2 Command Reference. ΓòÉΓòÉΓòÉ 5.9. QSYSTEM ΓòÉΓòÉΓòÉ QSYSTEM is a hardware detection utility that is supplied with OS/2.. You can use this utility to verify the hardware on your machine. Type QSYSTEM ? on the OS/2 command line to view the syntax of this utility. ΓòÉΓòÉΓòÉ 6. Sense Data ΓòÉΓòÉΓòÉ Sense data is an SNA-defined encoding of error information. Sense data can be found with: o APPC verbs - [MC_]ALLOCATE - [MC_]SEND_CONVERSATION o Error log entries o Alerts o Trace listings in the following entries: - A negative response - An UNBIND request - A Sense Data (X'7D') Management Services (MS) common subvector - A function management header type 7 (FMH-7) - An extended sense data control vector (X'35') Note: The easiest way to extract sense data from a trace listing is to use FMTTRACE +D and search in the detail output for Sense. This online document contains descriptions of all sense data issued by Communications Manager and the most common sense data received by Communications Manager. Information about sense data not described in this document can be found in SNA Network Product Formats. ΓòÉΓòÉΓòÉ 6.1. Sense Data Format ΓòÉΓòÉΓòÉ Sense data is a 4-byte field that includes: o A 1-byte category value o A 1-byte modifier value o 2 bytes of sense code specific information ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé Γöé Γöé Byte Γöé Byte Γöé Byte Γöé Byte Γöé Γöé 0 Γöé 1 Γöé 2 Γöé 3 Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé Γöé Γöé Γöé Sense code Γöé ΓöéCategoryΓöéModifierΓöé specific Γöé Γöé Γöé Γöé information Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé<ΓöÇΓöÇ Sense Code ΓöÇ>Γöé Γöé<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Sense Data ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>Γöé Together, the category byte 0, the modifier byte 1, and the sense code specific information, bytes 2 and 3, hold the sense data defined for the error condition that has occurred. ΓòÉΓòÉΓòÉ 6.2. Sense Code Categories ΓòÉΓòÉΓòÉ The following categories are defined: Value Category X'00' User Sense Data Only X'08' Request Reject X'10' Request Error X'20' State Error X'40' Request Header (RH) Usage Error X'80' Path Error All other sense code categories are reserved. Note: No discussion of sense data '00' is included in this document. ΓòÉΓòÉΓòÉ 6.3. X'08' Request Reject ΓòÉΓòÉΓòÉ This category indicates that the request was delivered to the intended component, and that it was understood and supported. However, the request was not executed. Select a sense code for specific information. 0801xxxx Resource Not Available 0805xxxx Session Limit Exceeded 0806xxxx Resource Unknown 0809xxxx Mode Inconsistency 080Cxxxx Procedure Not Supported 080Exxxx NAU Not Authorized 080Fxxxx End User Not Authorized 0812xxxx Insufficient Response 08130000 Bracket Bid Reject-No RTR Forthcoming 08140000 Bracket Bid Reject-No RTR Forthcoming 0815xxxx Function Active 08190000 RTR Not Required 081C0103 Request Not Executable 081E0000 Session Reference Error 08210002 Invalid Session Parameters 08240000 Logical Unit of Work Terminated 0835xxxx Invalid Parameter (with Pointer Only) 08390004 CP Architected TP Send Failure 083Bxxxx Invalid PCID 083E0001 Implementation-Defined Retry Limit Exhausted 0840xxxx Procedure Invalid for Resource 08460000 ERP Message Forthcoming 084Bxxxx Requested Resources Not Available 084C0000 Transaction Program Not Available-No Retry 08500001 Link Activation Limit Reached 08520001 Duplicate Session Activation Request 0857xxxx SSCP-LU Session is Not Active 08610002 Invalid COS Name 0864xxxx Function Terminated 086Cxx00 Required Control Vector or Subvector Missing 086Dxxxx Required Subfield Missing 086Fxxxx Length Error 0870xxxx Unformatted Subvector Value Invalid 0877xxxx Resource Mismatch 087Dxxxx Session Services Path Error 0889xxxx Transaction Program Error 088B0000 BB Not Accepted-BIS Reply Requested 088Cxxxx Missing Control Vector 088F0000 XRF Procedure Error 0890xxxx Search Failure 0891xxxx Invalid or Missing Invalid Network ID 0895xxxx Control Vector Error 0897xxxx System Definition Mismatch 08980003 XRF-Active Hierarchical Reset 08A0xxxx Session Reset 08A8xxxx Multiple-Domain Support Routing Exception 08A9xxxx Multiple-Domain Support Transaction Failure 08AAxxxx Required GDS Variable Missing 08B50000 Network Node Server Not Required ΓòÉΓòÉΓòÉ 6.3.1. 0801xxxx Resource Not Available ΓòÉΓòÉΓòÉ Explanation: The LU, PU, link station, or link specified in an RU is not available. For example, this sense data can occur when the workstation has both of the following: o A 3270 network connection directly to the host o A link to an SNA gateway, which is configured to support that workstation. If the gateway sends an ACTPU to the workstation before the host, the workstation rejects the ACTPU from the host with this sense data. The emulator logs this error as major error code 0042, minor error code 000002B2. Unless this situation is corrected, the host continues to send the ACTPU and each negative response causes an error to be logged. Operator Response: To correct this problem, do one of the following: o Change the configuration at the SNA gateway so that it no longer supports the workstation. o Change the configuration at the workstation so that its 3270 network connection is to the gateway. The possible values for bytes 2 and 3 are: 0000 0009 0012 ΓòÉΓòÉΓòÉ 6.3.1.1. 08010000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.1.2. 08010009 ΓòÉΓòÉΓòÉ The LU is not available because it is not ready to accept sessions. The local node has successfully issued a DELETE_LOCAL_LU or DELETE_PARTNER_LU verb. That LU is still in pending-delete state because it has active sessions with one or more partners. However, no new sessions can be started. ΓòÉΓòÉΓòÉ 6.3.1.3. 08010012 ΓòÉΓòÉΓòÉ An APPN connection cannot be established because this node has no available integers to represent a new transmission group (TG). ΓòÉΓòÉΓòÉ 6.3.2. 0805xxxx Session Limit Exceeded ΓòÉΓòÉΓòÉ Explanation: The requested session cannot be activated because one of the network accessible units (NAUs) has reached its session limit (such as the LU-LU session limit or the LU-mode session limit). This sense code applies to ACTCDRM, INIT, BIND, and CINIT requests. Operator Response: Ensure that each LU has a unique, fully qualified LU name in the same network. The possible values for bytes 2 and 3 are: 0000 0001 0002 0003 0004 0005 0006 0008 0009 000A 000B 000C ΓòÉΓòÉΓòÉ 6.3.2.1. 08050000 ΓòÉΓòÉΓòÉ Session limit has been exceeded. This could be the LU session limit, partner LU session limit, or the mode session limit. Review the configured values for each of these. One of the causes of an exceeded session limit is the presence of the same LU name on multiple machines in a single SNA network. LU names must be unique within a network as well as within a single machine. ΓòÉΓòÉΓòÉ 6.3.2.2. 08050001 ΓòÉΓòÉΓòÉ If accepted, the BIND request would prevent either the receiving LU or the sending LU from activating the number of contention winner sessions to the partner LU that were agreed on during a CNOS procedure. It is possible that two different LUs with the name in the network attempted to establish sessions with the same third, target LU. The target LU rejects the BIND issued by the later, duplicate named LU with this sense data. Each LU across every machine must have a unique, fully qualified LU name. ΓòÉΓòÉΓòÉ 6.3.2.3. 08050002 ΓòÉΓòÉΓòÉ If the BIND request had been accepted, it would have caused the XRF-backup session limit to be exceeded. ΓòÉΓòÉΓòÉ 6.3.2.4. 08050003 ΓòÉΓòÉΓòÉ If the BIND request had been accepted, it would have caused the XRF-active session limit to be exceeded. Note: The session limit for XRF-active sessions is 1. An XRF-active BIND is valid only if there are no XRF-active or XRF-backup sessions with the receiving SLU. ΓòÉΓòÉΓòÉ 6.3.2.5. 08050004 ΓòÉΓòÉΓòÉ For an independent LU, if the BIND request had been accepted, it would have caused the system-defined maximum number of sessions allowed for any LU to be exceeded for this LU. ΓòÉΓòÉΓòÉ 6.3.2.6. 08050005 ΓòÉΓòÉΓòÉ The intermediate session router is unable to create a session connector control block. The pool of session connectors is saturated with active sessions and with pending active sessions for which the queue bit was set in the BIND. Do not retry the BIND. ΓòÉΓòÉΓòÉ 6.3.2.7. 08050006 ΓòÉΓòÉΓòÉ The intermediate session router is unable to create a session connector control block. The pool of session connectors is saturated with active sessions and with pending active sessions for which the queue bit was not set in the BIND. Retry the BIND. ΓòÉΓòÉΓòÉ 6.3.2.8. 08050008 ΓòÉΓòÉΓòÉ For a dependent LU, if accepted, the BIND request would cause the session limit to be exceeded. ΓòÉΓòÉΓòÉ 6.3.2.9. 08050009 ΓòÉΓòÉΓòÉ If the request had been accepted, it would have caused the PLU session limit to be exceeded. ΓòÉΓòÉΓòÉ 6.3.2.10. 0805000A ΓòÉΓòÉΓòÉ If the request had been accepted, it would have caused the SLU session limit to be exceeded. ΓòÉΓòÉΓòÉ 6.3.2.11. 0805000B ΓòÉΓòÉΓòÉ The request was rejected because a session already exists between the same LU pair, and at least one of the LUs does not support parallel sessions. ΓòÉΓòÉΓòÉ 6.3.2.12. 0805000C ΓòÉΓòÉΓòÉ An LU-LU session was not established because a session already exists between the SLU and the session-controller PLU. ΓòÉΓòÉΓòÉ 6.3.3. 0806xxxx Resource Unknown ΓòÉΓòÉΓòÉ Explanation: The request contained a name or address not identifying a PU, LU, SSCP, link, or link station known to the receiver or the sender. Note: In an interconnected network environment, this sense code may be set by an SSCP in whose subnetwork and domain the LU was expected to reside. It is not set by an SSCP that is only an intermediary on the session-setup path. A gateway SSCP examines the Resource Identifier control vector in a session setup request (for example, CDINIT), to determine whether the LU is in the SSCP's subnetwork and domain. The possible values for bytes 2 and 3 are: 0000 0001 0002 0004 0006 0007 0008 0009 000A 0011 0012 0013 0014 0015 0016 0017 0018 0021 0022 0023 0024 0025 0026 0027 0028 0029 002A 002B 002C 002F 0030 ΓòÉΓòÉΓòÉ 6.3.3.1. 08060000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.3.2. 08060001 ΓòÉΓòÉΓòÉ The resources identified in an SNA Address List (X'04') MS common subvector are unknown to the PU receiving the request. Note: When this sense data flows in a -RSP(NMVT), the referenced X'04' subvector is the one that was present in the corresponding request NMVT. When this sense data flows in a Sense Data (X'7D') MS common subvector, the referenced X'04' subvector is present with the X'7D' subvector in the same major vector. ΓòÉΓòÉΓòÉ 6.3.3.3. 08060002 ΓòÉΓòÉΓòÉ Set aside for implementation-specific use, and is not otherwise defined in SNA; see implementation documentation for details of usage. ΓòÉΓòÉΓòÉ 6.3.3.4. 08060004 ΓòÉΓòÉΓòÉ The indicated resources in the accompanying Name List (X'06') subvector are unknown to the control point to which the request containing the subvector was routed. Note: Names in the hierarchy below the level of the first unknown resource are not examined by the control point. ΓòÉΓòÉΓòÉ 6.3.3.5. 08060006 ΓòÉΓòÉΓòÉ For a dynamic reconfiguration DELETE, MOVE, or REPLACE operation, the resource to be dynamically reconfigured could not be found. ΓòÉΓòÉΓòÉ 6.3.3.6. 08060007 ΓòÉΓòÉΓòÉ The LU address in bytes 8 and 9 of RNAA type X'4' is already in the free pool. ΓòÉΓòÉΓòÉ 6.3.3.7. 08060008 ΓòÉΓòÉΓòÉ For a dynamic reconfiguration DELETE, MOVE, or REPLACE operation, the NAU name in RNAA does not correspond to the resource identified by the element address in the RNAA. ΓòÉΓòÉΓòÉ 6.3.3.8. 08060009 ΓòÉΓòÉΓòÉ The SSCP(OLU) cannot identify the SSCP(DLU), and default SSCP rerouting is not enabled. ΓòÉΓòÉΓòÉ 6.3.3.9. 0806000A ΓòÉΓòÉΓòÉ The configuration identifier specified in a Management Services command is not recognized by the DLC manager at the receiving node. ΓòÉΓòÉΓòÉ 6.3.3.10. 08060011 ΓòÉΓòÉΓòÉ An unknown OLU name was specified in the request. For example, this situation can occur when a local node is using an LU that is unknown to the subarea. Ensure that all local LUs that establish sessions with a subarea host are configured at the host. ΓòÉΓòÉΓòÉ 6.3.3.11. 08060012 ΓòÉΓòÉΓòÉ An unknown DLU name was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.12. 08060013 ΓòÉΓòÉΓòÉ An unknown SLU name was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.13. 08060014 ΓòÉΓòÉΓòÉ An unknown PLU name was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.14. 08060015 ΓòÉΓòÉΓòÉ An unknown OLU address was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.15. 08060016 ΓòÉΓòÉΓòÉ An unknown DLU address was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.16. 08060017 ΓòÉΓòÉΓòÉ An unknown SLU address was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.17. 08060018 ΓòÉΓòÉΓòÉ An unknown PLU address was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.18. 08060021 ΓòÉΓòÉΓòÉ The session-initiation request specified that the receiving SSCP is the SSCP having the DLU in its domain, but the DLU is unknown to the receiving SSCP. ΓòÉΓòÉΓòÉ 6.3.3.19. 08060022 ΓòÉΓòÉΓòÉ The originator of the request is unknown to the receiver. ΓòÉΓòÉΓòÉ 6.3.3.20. 08060023 ΓòÉΓòÉΓòÉ The destination of the request or response is unknown to the sender. ΓòÉΓòÉΓòÉ 6.3.3.21. 08060024 ΓòÉΓòÉΓòÉ An unknown LU1 name was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.22. 08060025 ΓòÉΓòÉΓòÉ An unknown LU2 name was specified in the request. ΓòÉΓòÉΓòÉ 6.3.3.23. 08060026 ΓòÉΓòÉΓòÉ The SSCP does not have a session with the boundary function PU of an independent LU. ΓòÉΓòÉΓòÉ 6.3.3.24. 08060027 ΓòÉΓòÉΓòÉ The PU associated with a switched SLU is unknown. Session setup processing for the switched SLU cannot proceed. ΓòÉΓòÉΓòÉ 6.3.3.25. 08060028 ΓòÉΓòÉΓòÉ NAU1 network address is unknown. ΓòÉΓòÉΓòÉ 6.3.3.26. 08060029 ΓòÉΓòÉΓòÉ NAU2 network address is unknown. ΓòÉΓòÉΓòÉ 6.3.3.27. 0806002A ΓòÉΓòÉΓòÉ The NAU name in the CONTACT or ACTLU does not correspond to the resource at the target address. ΓòÉΓòÉΓòÉ 6.3.3.28. 0806002B ΓòÉΓòÉΓòÉ The TG being activated is unknown. Local or network topology information may be incorrect. This can occur because of one of the following conditions: o The local node is trying to use an "activatable on demand" link, but could not activate the link. This could happen for any of the reasons a link activation can fail: the link was defined wrong, the remote node is not powered on, and so on. o An "activatable on demand" link is defined in the reverse direction from where the local node is trying to go. To correct this, either make your local link "activatable on demand" or change the configuration at the remote node so that it is not "activatable on demand." o There is an inconsistency among the topology databases in the APPN network. One way to spot inconsistencies is to use subsystem management to view the topology information. Check if there are any links shown as active that are not actually active. To reset this condition in the local workstation, stop and restart Communications Manager. If this condition persists, report it to your local support personnel. ΓòÉΓòÉΓòÉ 6.3.3.29. 0806002C ΓòÉΓòÉΓòÉ The identification in either the Node Identification field or the control point (CP) name in a received XID3 is different from what this node was configured to expect. ΓòÉΓòÉΓòÉ 6.3.3.30. 0806002F ΓòÉΓòÉΓòÉ The destination resource was not found on this node during a session activation attempt. ΓòÉΓòÉΓòÉ 6.3.3.31. 08060030 ΓòÉΓòÉΓòÉ The adjacent node was not identified during CP-CP session activation. ΓòÉΓòÉΓòÉ 6.3.4. 0809xxxx Mode Inconsistency ΓòÉΓòÉΓòÉ Explanation: The requested function cannot be performed in the present state of the receiver. The possible values for bytes 2 and 3 are: 0000 000A 0039 003A 003C 003D 003E 0040 0045 0046 0047 0049 0054 ΓòÉΓòÉΓòÉ 6.3.4.1. 08090000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.4.2. 0809000A ΓòÉΓòÉΓòÉ The partner data link control (DLC) is not activated. Generally, a long time-out (for example, 30 seconds) occurs before the verb returns. Possible reasons this occurs are: o The target machine is not powered on. o The target data link control (DLC) is not activated. o The target MAC address is wrong. o Maximum number of links is exceeded. o All links configured in the local workstation are incoming. o Different service access points (SAPs) are defined. ΓòÉΓòÉΓòÉ 6.3.4.3. 08090039 ΓòÉΓòÉΓòÉ This is a CP transaction error. CP Capabilities (X'12C1') generalized data stream (GDS) variable request sent indicating conversation complete or without change direction (for example, CEB or ╨║CD) or CP Capabilities reply sent indicating conversation not yet complete (for example, ╨║CEB). ΓòÉΓòÉΓòÉ 6.3.4.4. 0809003A ΓòÉΓòÉΓòÉ A null XID was received when an XID3 with its exchange state indicators set to prenegotiation, negotiation proceeding, or exchange state indicators not supported was expected. ΓòÉΓòÉΓòÉ 6.3.4.5. 0809003C ΓòÉΓòÉΓòÉ An XID3 with the exchange state indicators set to prenegotiation was received when either of the values negotiation proceeding or exchange state indicators not supported was expected. ΓòÉΓòÉΓòÉ 6.3.4.6. 0809003D ΓòÉΓòÉΓòÉ A nonactivation XID3 was received when a null XID or link activation XID3 was expected. ΓòÉΓòÉΓòÉ 6.3.4.7. 0809003E ΓòÉΓòÉΓòÉ A link activation XID3 was received when a null XID or nonactivation XID3 was expected. ΓòÉΓòÉΓòÉ 6.3.4.8. 08090040 ΓòÉΓòÉΓòÉ A mode-setting command was received and was either not expected or invalid for the receiving node. For example, SNRME was received when SNRM was expected. ΓòÉΓòÉΓòÉ 6.3.4.9. 08090045 ΓòÉΓòÉΓòÉ An XID3 indicating that the sender does not support the exchange state indicators was received when the sender previously indicated support for this field in XID3. ΓòÉΓòÉΓòÉ 6.3.4.10. 08090046 ΓòÉΓòÉΓòÉ An XID3 indicating that the sender supports the exchange state indicators was received when the sender previously indicated that it does not support this field in XID3. ΓòÉΓòÉΓòÉ 6.3.4.11. 08090047 ΓòÉΓòÉΓòÉ An XID was received. Once a node sends one of these mode setting commands, no additional XIDs may be sent. ΓòÉΓòÉΓòÉ 6.3.4.12. 08090049 ΓòÉΓòÉΓòÉ An XID3 containing the XID Negotiation Error (X'22') was received by this node. ΓòÉΓòÉΓòÉ 6.3.4.13. 08090054 ΓòÉΓòÉΓòÉ The adjacent node is not the node type that the receiving node was configured to expect. The received negotiation-proceeding XID3 indicated that the adjacent node is an APPN end node, while this node expected the adjacent node to be an APPN network node, or vice versa. ΓòÉΓòÉΓòÉ 6.3.5. 080Cxxxx Procedure Not Supported ΓòÉΓòÉΓòÉ Explanation: A procedure (Test, Trace, IPL, REQMS type, MS major vector key) specified in an RU is not supported by the receiver. The possible values for bytes 2 and 3 are: 0005 0006 0012 0013 01xx ΓòÉΓòÉΓòÉ 6.3.5.1. 080C0005 ΓòÉΓòÉΓòÉ The Management Services (MS) major vector key is not supported by the receiver. This may occur for one of these reasons: o APPC sent an NMVT to the host using its active SSCP-PU session. At the host, one of two things occurred: - There was no network management application available (such as NetView) to handle the NMVT. - The network management application on the host does not support the Management Services (MS) major vector key sent by APPC. When the host replied that it could not handle the NMVT, APPC wrote this error log entry. o NetView or a NetView application on the host sent an NMVT request to APPC which was not recognized. For example, major error code . . . . . . . . . . . . . . . . . . : 0012 minor error code . . . . . . . . . . . . . . . . . . : 080C0005 Originator . . . . . . . . . . . . . : APPC Conversation ID. . . . . . . . . . . : 00000000 Process ID . . . . . . . . . . . . . : 1000 Error data . . . . . . . . . . . . . : 2C00000000010B800041038D000000000000218080049288001994ED00EC0000000100 00000000000004000A0014003200642020202020202020202020202020202020202020 2020202020202020202020202020202020202020202020202020202020202020202020 In this example, the first 9 bytes are the TH and RH. The next 3 bytes, X'41038D', indicate an NS header for NMVT. For more information about NS headers for NMVT, refer to Systems Network Architecture Product Formats. The major vector length is X'0021' bytes, and its key is X'8080'. This key indicates a request for response time monitoring (RTM). Because APPC does not handle this major vector, APPC logs this entry. ΓòÉΓòÉΓòÉ 6.3.5.2. 080C0006 ΓòÉΓòÉΓòÉ The Management Services (MS) major vector is identified as one that contains a command, but the receiver does not recognize or support the command subvector. A control subvector is missing or not supported. Communications Manager, not being a focal point product, does not know how to process a X'63', so it sends an SNACR rather than a X'64' reject. If the command subvector is identified, but an additional required subvector is missing, refer to X'086C' sense code in Systems Network Architecture Product Formats. ΓòÉΓòÉΓòÉ 6.3.5.3. 080C0012 ΓòÉΓòÉΓòÉ Application generalized data stream (GDS) variable in a multiple-domain support message unit (MDS MU) not supported. ΓòÉΓòÉΓòÉ 6.3.5.4. 080C0013 ΓòÉΓòÉΓòÉ MDS message type not supported. Receiving node does not support the MDS message type in this MDS MU. ΓòÉΓòÉΓòÉ 6.3.5.5. 080C01xx ΓòÉΓòÉΓòÉ A subvector in a Management Services (MS) major vector is identified as one inside that the receiver requires one of several supported subfields, but none of these subfields is present. Byte 3 contains the key (xx) of the subvector. ΓòÉΓòÉΓòÉ 6.3.6. 080Exxxx NAU Not Authorized ΓòÉΓòÉΓòÉ Explanation: The requesting network addressable unit (NAU) does not have access to the requested resource. Operator Response: Define that APPN network node as your NN server, or send the BIND request to the currently defined NN server. The possible values for bytes 2 and 3 are: 0002 0006 0009 000B ΓòÉΓòÉΓòÉ 6.3.6.1. 080E0002 ΓòÉΓòÉΓòÉ A gateway T4 node received a dynamic dump request from an SSCP that is not in the native network of the gateway T4 node. ΓòÉΓòÉΓòÉ 6.3.6.2. 080E0006 ΓòÉΓòÉΓòÉ An APPN network node received a Register from an unauthorized APPN end node. ΓòÉΓòÉΓòÉ 6.3.6.3. 080E0009 ΓòÉΓòÉΓòÉ An APPN network node received a Delete from an unauthorized APPN end node. ΓòÉΓòÉΓòÉ 6.3.6.4. 080E000B ΓòÉΓòÉΓòÉ A LOCATE/CDINIT was received from a node that is not defined as a client APPN end node. This can be detected by either DS or SS. For example, a BIND request came into an APPN network node that is not the APPN network node server of the BIND-sending end node. The APPN network node is unable to handle this type of request. ΓòÉΓòÉΓòÉ 6.3.7. 080Fxxxx End User Not Authorized ΓòÉΓòÉΓòÉ The possible values for bytes 2 and 3 are: 0000 07F1 6051 ΓòÉΓòÉΓòÉ 6.3.7.1. 080F0000 End User Not Authorized ΓòÉΓòÉΓòÉ This indicates that the BIND is correct, but the primary LU has not been authorized to activate the requested session. ΓòÉΓòÉΓòÉ 6.3.7.2. 080F07F1 End User Not Authorized ΓòÉΓòÉΓòÉ The requesting end user does not have access to the requested resource. ΓòÉΓòÉΓòÉ 6.3.7.3. 080F6051 Access Security Information Invalid ΓòÉΓòÉΓòÉ The request specifies an Access Security Information field that is unacceptable to the receiver. For security reasons, no further detail on the error is provided. This sense data is sent in FMH-7 or UNBIND. The partner LU rejected the user ID or password received on an incoming attach. An example of when this situation occurs is: o The remote location is using Communications Manager and the TP definition specifies Conversation security(YES). The APPC attach manager searched its list of valid user IDs and passwords, but did not find the received combination. Programmer Response: Either the [MC_]ALLOCATE or [MC_]CONVERSATION verb issued by the local program has a wrong user_id or password parameter, or the remote configuration needs to be changed. Look at the verb control block being used for this verb. Verify that it specifies valid user_id and password parameters. Operator Response: If the problem is with the remote configuration, ensure that the user ID and password combination has been correctly defined there. User IDs and passwords are two of the few APPC configuration fields that are case sensitive. Be sure that the combination of uppercase and lowercase letters matches those specified in the program. Also ensure that if these are required (see the remote location's TP definition), they are accepted by the partner LU (see the remote location's definition of its partner LU). If the remote location is using Communications Manager, look at its error log. Find an error log entry of major error code 001A; its minor error code indicates why this attach was rejected. The configuration is changed. ΓòÉΓòÉΓòÉ 6.3.8. 0812xxxx Insufficient Resource ΓòÉΓòÉΓòÉ Explanation: Receiver cannot act on the request because of a temporary lack of resources. The possible values for bytes 2 and 3 are: 0000 0007 000A 000D 0010 ΓòÉΓòÉΓòÉ 6.3.8.1. 08120000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.8.2. 08120007 ΓòÉΓòÉΓòÉ Insufficient resources are available for LU address allocation. ΓòÉΓòÉΓòÉ 6.3.8.3. 0812000A ΓòÉΓòÉΓòÉ An APPN network node does not have adequate resources to perform the Register. For example, the available directory capacity is exceeded. ΓòÉΓòÉΓòÉ 6.3.8.4. 0812000D ΓòÉΓòÉΓòÉ Insufficient buffers exist to activate a session. ΓòÉΓòÉΓòÉ 6.3.8.5. 08120010 ΓòÉΓòÉΓòÉ The control point (CP) does not have adequate resources to process a Locate generalized data stream (GDS) variable request. The contention loser's CP-CP session is deactivated. ΓòÉΓòÉΓòÉ 6.3.9. 08130000 Bracket Bid Reject-No RTR Forthcoming ΓòÉΓòÉΓòÉ Explanation: BID (or BB) was received while the first speaker was in the in-bracket state, or while the first speaker was in the between-brackets state and the first speaker denied permission. RTR is not sent. For LU 6.2, this is the only setting defined. ΓòÉΓòÉΓòÉ 6.3.10. 08140000 Bracket Bid Reject-RTR Forthcoming ΓòÉΓòÉΓòÉ Explanation: BID (or BB) was received while the first speaker was in the in-bracket state, or while the first speaker was in the between-brackets state and the first speaker denied permission. RTR is sent. For LU 6.2, this is the only setting defined. ΓòÉΓòÉΓòÉ 6.3.11. 0815xxxx Function Active ΓòÉΓòÉΓòÉ Explanation: A request to activate a network element or procedure was received, but the element or procedure was already active. The possible values for bytes 2 and 3 are: 0000 0004 0007 ΓòÉΓòÉΓòÉ 6.3.11.1. 08150000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.11.2. 08150004 ΓòÉΓòÉΓòÉ A BIND was received from a T2.1 node when the session is already active. For example, the LFSID is in use. The receiver rejects the BIND. ΓòÉΓòÉΓòÉ 6.3.11.3. 08150007 ΓòÉΓòÉΓòÉ A session activation request was received by an APPN network node or an APPN end node to activate a CP-CP session that was already active. ΓòÉΓòÉΓòÉ 6.3.12. 08190000 RTR Not Required ΓòÉΓòÉΓòÉ Explanation: Receiver of Ready To Receive has nothing to send. ΓòÉΓòÉΓòÉ 6.3.13. 081C0103 Request Not Executable ΓòÉΓòÉΓòÉ Explanation: The requested function cannot be executed because of a permanent error condition in the receiver. X'0103' indicates that the remote node is not responding to polling requests. The remote node may be powered off or the hardware may be functioning incorrectly. ΓòÉΓòÉΓòÉ 6.3.14. 081E0000 Session Reference Error ΓòÉΓòÉΓòÉ Explanation: The request referred to a half-session that either could not be found or was not in the expected state (generally applies to network services requests). ΓòÉΓòÉΓòÉ 6.3.15. 08210002 Invalid Session Parameters ΓòÉΓòÉΓòÉ Explanation: Session parameters were not valid or not supported by the half-session whose activation was requested. X'0002' indicates that the specified mode name was not recognized by the control point (CP). ΓòÉΓòÉΓòÉ 6.3.16. 08240000 Logical Unit of Work Terminated ΓòÉΓòÉΓòÉ Explanation: The current unit of work has been terminated; when sync point protocols are in use, both sync point managers revert to the previously committed sync point. For LU 6.2, this sense data is send-only FMH-7. X'0000' indicates that for LU 6.2, backout initiated-no resync in progress. A transaction program or its LU has initiated backout. The protected resources for the distributed logical unit of work are to be restored to the previously committed sync point. When sent in reply to a PS header, no resync in progress means that all resources in the transaction subordinate to the backout sender have backed out. ΓòÉΓòÉΓòÉ 6.3.17. 0835xxxx Invalid Parameter (with Pointer Only) ΓòÉΓòÉΓòÉ Explanation: The request contained a fixed- or variable-length field whose contents are invalid or not supported by the network accessible unit (NAU) that received the request. xxxx Bytes 2 and 3 contain a 2-byte binary count that indexes (0-origin) the first byte of the fixed- or variable-length field having invalid contents. If the index points to a partner LU name field that is not recognized, it is possible that the partner will reject the bind because the partner LU is not explicitly defined and does not allow implicit support. If this occurs, ensure that the partner LU is defined by either defining the DEFINE_PARTNER_LU verb or by setting the IMPLICIT_INBOUND_PLU_SUPPORT parameter of the DEFINE_DEFAULTS verb in the .NDF file to YES. The error usually indicates that the BIND was rejected by APPC because of a syntax, state, or semantic error and points to an offset in the RU field of the invalid parameter. Example: A problem occurs when establishing an LU 6.2 session between a PS/2 program running Communications Manager program and an MVS host running VTAM* 3.1.1. The configuration is as follows: ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé PS/2 Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ 3174 Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ MVS/XA Γöé PS/2 LU defined to Γöé Token Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé VTAM 3.1.1 Γöé VTAM with a logmode Γöé Ring Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ for LU 6.2 ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé CTC Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé MVS/XA guest Γöé Γöé under VM with Γöé Γöé VTAM 3.1.1 Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Host status messages are sent to the PS/2 workstation where they are filtered and displayed for an operator's action. Communications Manager is configured for APPC using an IBM Token-Ring Network 16/4 Adapter/A. On the host side, the application carries out the following: o Successfully issues an OPEN for an ACB with MACRF=NLOGON. o Issues an OPNDST as follows: OPNDST OPTCD=(ACQUIRE,CONALL,SYN,CA),NIB=AINIB,RPL=AIRPL, X AAREA=ACAREA,AAREALN=255 AIACB ACB AM=VTAM,APPLID=AIHOST,EXLST=AIXLST,MACRF=NLOGON AICOUNT DC F'0' AIRPL RPL AM=VTAM,NIB=AINIB,ACB=AIACB AINIB NIB NAME=BHT1505,EXLST=AIXLST,MODE=RECORD,PROC=NEGBIND, X BNDAREA=PCAREA AIXLST EXLST AM=VTAM,LERAD=AISYNLER,SYNAD=AISYNLER AIGOOD DC F'0' AISAVE DS 15F AIHOST DC X'08',CL8'RTX1' PCAREA DC X'001307B0B050B5000085850000060200000000000000002C0000' DC X'04D9E3E7F1' ACAREA DC XL255'00' The PU, LU, and log mode definitions follow: BHT1505P PU CUADDR=B05,ISTATUS=ACTIVE,PUTYPE=2,MAXBFRU=10, USSTAB=USSTABTS,MODETAB=SCCMODE,SSCPFM=USSSCS BHT1505 LU LOCADDR=2,DLOGMOD=APPC,USSTAB=ISTINCDT, SPAN=(HLPDSK01) APPC MODEENT LOGMODE=APPC,FMPROF=X'13',TSPROF=X'07', PRIPROT=X'B0',SECPROT=X'B0',COMPROT=X'50B1' RUSIZES=X'8888',PSERVIC=X'060200000000000000002C00', TYPE=0 Example: For the following error, the offset appears to be at the end of the Primary LU name field, which is being correctly sent as RTX1. The following is a portion of the trace. ===RECV====> IBMTRNET #00 40002000000104 00003F186A10C08C #:3400 TH:2D000202069C RH:6B8000 31001307 B0B050B5 80018585 01000602 <1.....P...ee....> 00000000 00000000 2C000004 D9E3E7F1 <........,...RTX1> 000008C2 C8E3F1F5 F0F540 <...BHT1505. > <==SEND===== IBMTRNET #00 40002000000104 00003F186A10C08C #:0E00 TH:2D000202069C RH:EF9000 08350020 31 <.5. 1 > This IBMTRNET trace shows that a BIND request was received and a -RSP(08350020) was returned. X'0835' indicates that the BIND request contains an invalid parameter and X'0020' is the offset where the error was found. X'0020' does not point to the Primary LU name field; it points to the first byte after the Primary LU name field. The offset starts from the beginning of the RU, not from the beginning of the TH or RH. Normally, this position in the BIND request contains the User data field. The User data field contains structured subfields (for example, the mode name, the fully qualified PLU name, the fully qualified SLU name, and the session instance identifier). Note that your BIND has X'00' in this position. This is a valid value and indicates that there is no User data field. In particular, this value means that the host has not specified a mode name (or more accurately, has specified the null mode name). However, versions of Communications Manager prior to Extended Services could not be configured to accept an all-blank mode name. This pre-Extended Services workstation is rejecting the BIND because it has not been configured (and cannot be configured) to accept a null mode name. An all-blank mode name is predefined in Extended Services and Communications Manager/2. Note: This sense code is not used to report an invalid value in a Management Services (MS) major vector. If the invalid value occurs in a formatted Management Services (MS) subvector, sense code X'086B' is used. If it occurs in an unformatted subvector, sense code X'0870' is used. ΓòÉΓòÉΓòÉ 6.3.18. 08390004 CP architected TP send failure ΓòÉΓòÉΓòÉ Explanation: Deactivate both contention winner and contention loser CP-CP sessions. For example, a failure can occur when a network node attempts to issue a broadcast search to a particular node and the node does not respond within a time-out period. An UNBIND request is sent to the problem node and the session is deactivated. ΓòÉΓòÉΓòÉ 6.3.19. 083Bxxxx Invalid PCID ΓòÉΓòÉΓòÉ Explanation: The received procedure correlation identification (PCID) for a new session duplicated the PCID assigned to another session, or the received PCID intended as an identifier for an existing session could not be associated with such an existing session, or an error was detected in the format of the received PCID. The possible values for bytes 2 and 3 are: 0001 0002 ΓòÉΓòÉΓòÉ 6.3.19.1. 083B0001 ΓòÉΓòÉΓòÉ The PCID contained in CDINIT (Initiate or Queue), INIT-OTHER-CD, or CDTAKED duplicates a PCID received previously in one of these requests. ΓòÉΓòÉΓòÉ 6.3.19.2. 083B0002 ΓòÉΓòÉΓòÉ The received fully qualified PCID duplicated one assigned to another session. ΓòÉΓòÉΓòÉ 6.3.20. 083E0001 Implementation-Defined Retry Limit Exhausted ΓòÉΓòÉΓòÉ Explanation: X'0001' indicates that the implementation-defined limit on XID exchanges was exceeded before link activation completed. ΓòÉΓòÉΓòÉ 6.3.21. 0840xxxx Procedure Invalid for Resource ΓòÉΓòÉΓòÉ Explanation: The received RU is not supported in the receiver for this type of resource. For example: o SETCV specifies boundary function support for a type 1 node, but the capability is not supported by the receiving node. o The PU receiving an EXECTEST or TESTMODE is not the primary PU for the target link. The possible values for bytes 2 and 3 are: 0007 0008 000C ΓòÉΓòÉΓòÉ 6.3.21.1. 08400007 ΓòÉΓòÉΓòÉ Resource not found. A Delete or Find could not be satisfied because the specified entry does not exist in the receiver's directory and the resource cannot be found in the network. The target LU may be owned by an APPN network node server that cannot be contacted, or it might not exist in the network at all. If the partner LU is located at an adjacent LEN node, ensure that a DEFINE_PARTNER_LU_LOCATION exists for that LU in the SNA configuration file and that there is a connection to its owning node. ΓòÉΓòÉΓòÉ 6.3.21.2. 08400008 ΓòÉΓòÉΓòÉ Directory entry cannot be deleted. An APPN network node received a Delete with a delete entry condition indicating that the entry can be deleted only if it has no subordinate entries. Since the entry does have subordinate entries, the Delete is rejected. ΓòÉΓòÉΓòÉ 6.3.21.3. 0840000C ΓòÉΓòÉΓòÉ Conflicting entry type on delete. The Delete request attempted to delete a home entry. For example, one defined at the receiver by its own network operator facility (NOF). ΓòÉΓòÉΓòÉ 6.3.22. 08460000 ERP Message Forthcoming ΓòÉΓòÉΓòÉ Explanation: The received request was rejected for a reason to be specified in a forthcoming request. ΓòÉΓòÉΓòÉ 6.3.23. 084Bxxxx Requested Resources Not Available ΓòÉΓòÉΓòÉ Explanation: Resources named in the request, and required to honor it, are not currently available. It is not known when the resources are made available. Programmer Response: Retry the allocation request. However, to avoid congesting the network with attempted allocation requests, your local program should pause or wait for a keystroke before retrying the conversation. Operator Response: Start the APPC attach manager, increase the incoming_allocate_timeout, and increase the incoming_allocate_queue_depth in the configuration at the remote location, if appropriate. If the remote location is using Communications Manager, the remote program may have ended before issuing a RECEIVE_ALLOCATE verb to receive the queued attach. If this action is unexpected, check the following conditions in the remote location: o The remote program may be failing to issue the RECEIVE_ALLOCATE verbs correctly. o The remote program may be issuing the RECEIVE_ALLOCATE verbs with an incorrect tp_name. o The filespec field configured at the remote location could be incorrect. If the remote location is using Communications Manager, look at its error log. Find an error log entry of major error code 0020; its minor error code indicates why this attach was rejected. The possible values for bytes 2 and 3 are: 0000 0003 6031 ΓòÉΓòÉΓòÉ 6.3.23.1. 084B0000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.23.2. 084B0003 ΓòÉΓòÉΓòÉ Management services has temporarily been unable to allocate OS/2 system resources to satisfy the request. Retry the request. ΓòÉΓòÉΓòÉ 6.3.23.3. 084B6031 ΓòÉΓòÉΓòÉ Transaction program not available-Retry allowed. The FMH-5 attach command specifies a transaction program that the receiver is unable to start. Either the program is not authorized to run or the resources to run it are not available now. The condition is temporary. The sender is responsible for subsequent retry. This sense data is sent only in FMH-7. The partner LU rejected the incoming attach because it could not start the specified program immediately. If the partner LU is associated with an APPC attach manager, some possible causes of this sense data are: o The APPC attach manager associated with the partner LU is stopped. o The attach manager associated with the partner LU is stopped. This can be caused by a missing START_ATTACH_MANAGER statement in your local SNA configuration file. Ensure that the START_ATTACH_MANAGER statement is configured to be started. o The incoming_allocate_timeout defined in the TP definition at the partner LU is 0 or is too short. This only applies if the partner TP is configured as Queued. o The local transaction program has specified an incorrect tp_name on its [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb. o The incoming_allocate_queue_depth configured in the TP definition at the partner LU is too small. This only applies if the partner TP is configured as Queued. o At the remote location, the incoming attach was queued, waiting to be processed. The intended program was remotely started, but ended before it could process the queued incoming attach. APPC wrote an error log entry of major error code 0001, minor error code 084B6031 to the error log in the local workstation. ΓòÉΓòÉΓòÉ 6.3.24. 084C0000 Transaction Program Not Available-No Retry ΓòÉΓòÉΓòÉ Explanation: Receiver cannot act on the request because resources required to honor the request are permanently unavailable. The sender should not retry immediately because the situation is not transient. X'0000' shows that for LU 6.2, the FMH-5 attach command specifies a transaction program that the receiver is unable to start. The condition is not temporary. The sender should not retry immediately. This sense data is sent only in FMH-7. The partner LU rejected the incoming attach because it could not start the specified program. Possible reasons for this error are: o The intended program does not exist at the remote location. o If the remote location is using Communications Manager, its TP definition may be configured with the wrong filespec parameter, or the filespec for the TP may be spelled wrong. o The operating system or communications subsystem at the remote location has exhausted its available resources and is unable to start the remotely attachable program. If the remote location is using Communications Manager, the APPC attach manager at the remote location may have failed to start the program because of an OS/2 error on its internal DosExecPgm or DosStartSession function call. Any of the nonzero OS/2 return codes from these function calls may cause this situation. For example, the remote location is running Communications Manager and the remotely attachable program is attach-manager-started. If there is insufficient memory for the attach manager to start the program, the incoming attach is rejected with this sense data. This could also occur if the remote location has used all of its processes or screen groups. APPC wrote an error log entry of major error code 0001, minor error code 084C0000 to the error log in the local workstation. Programmer Response: Do not retry the allocation request. Operator Response: Ensure that the intended program is defined correctly at the remote location, and that it is compiled and linked correctly for its operating system. If the remote location is using Communications Manager, look at its error log for more information. ΓòÉΓòÉΓòÉ 6.3.25. 08500001 Link Activation Limit Reached ΓòÉΓòÉΓòÉ Explanation: The specified transmission group (TG) was not activated because the maximum number of active link stations allowed on this port has already been reached. ΓòÉΓòÉΓòÉ 6.3.26. 08520001 Duplicate Session Activation Request ΓòÉΓòÉΓòÉ Explanation: A second BIND has been received from a peripheral node PLU while the session was still in the activation process. ΓòÉΓòÉΓòÉ 6.3.27. 0857xxxx SSCP-LU session is not active ΓòÉΓòÉΓòÉ Explanation: The SSCP-LU session required for the processing of the request is not active; for example, in processing REQECHO, the SSCP did not have an active session with the target LU named in the REQECHO RU. The possible values for bytes 2 and 3 are: 0000 0001 0002 0003 0004 ΓòÉΓòÉΓòÉ 6.3.27.1. 08570000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.27.2. 08570001 ΓòÉΓòÉΓòÉ The SSCP-SLU session is in the process of being reactivated. ΓòÉΓòÉΓòÉ 6.3.27.3. 08570002 ΓòÉΓòÉΓòÉ The SSCP-PLU session is inactive. ΓòÉΓòÉΓòÉ 6.3.27.4. 08570003 ΓòÉΓòÉΓòÉ The SSCP-SLU session is inactive. ΓòÉΓòÉΓòÉ 6.3.27.5. 08570004 ΓòÉΓòÉΓòÉ The SSCP-PLU session is in the process of being reactivated. ΓòÉΓòÉΓòÉ 6.3.28. 08610002 Invalid COS Name ΓòÉΓòÉΓòÉ Explanation: The class of service name generated by the T2.1 control point (CP) local to, or the T2.1 NNCP server for, the initiating LU is not in the class of service name definition table. ΓòÉΓòÉΓòÉ 6.3.29. 0864xxxx Function Terminated ΓòÉΓòÉΓòÉ Explanation: The conversation was terminated abnormally. Other terminations could occur after repeated executions. The request sender is responsible detecting such a loop. The possible values for bytes 2 and 3 are: 0000 0001 0002 ΓòÉΓòÉΓòÉ 6.3.29.1. 08640000 ΓòÉΓòÉΓòÉ Premature conversation termination. For LU 6.2, the conversation is terminated abnormally; for example, the transaction program may have issued a DEALLOCATE_ABEND verb, or the program may have terminated (normally or abnormally) without explicitly terminating the conversation. This sense data is sent only in FMH-7 or UNBIND. For non-LU 6.2, no additional information is specified. ΓòÉΓòÉΓòÉ 6.3.29.2. 08640001 ΓòÉΓòÉΓòÉ System logic error-No retry. Either the local side or the remote side issued a DEALLOCATE verb with the type(ABEND_SVC) parameter. A possible cause is that the remote TP at the partner was deactivated while it was running. This can be done by the partner using subsystem management. The TP_ENDED verb issued by the partner generates a DEALLOCATE verb with the type(ABEND_SVC) parameter to be issued internally by APPC. ΓòÉΓòÉΓòÉ 6.3.29.3. 08640002 ΓòÉΓòÉΓòÉ Excessive elapsed time-No retry. Excessive time has elapsed while waiting for a required action or event. For example, a transaction program has failed to issue a conversation-related protocol boundary verb. No retry of the conversation should be attempted. This sense data is sent in UNBIND when there is no chain to respond to; otherwise, it is sent in FMH-7. Either the local side or the remote side issued a DEALLOCATE verb with type(ABEND_TIMER). This error log is generated whenever a local verb receives DEALLOC_ABEND_TIMER(APPC primary return code 0008). ΓòÉΓòÉΓòÉ 6.3.30. 086Cxx00 Required Control ΓòÉΓòÉΓòÉ Vector or Subvector Missing Explanation: One or more control vectors or Management Services (MS) subvectors that are required by the receiver to perform some function are missing from the received messages or are not present in the required position. Byte 2 following the sense code contains the key (xx) of one of the control vectors or subvectors that is missing or improperly positioned. Byte 3 is reserved (00). Note: See 080C0006 sense data for the case in which the major vector key is recognized, but a subvector representing the function to be performed cannot be identified. ΓòÉΓòÉΓòÉ 6.3.31. 086Dxxxx Required Subfield Missing ΓòÉΓòÉΓòÉ Explanation: A control vector or Management Services (MS) subvector lacks one or more subfield keys that are required by the receiver to perform the function requested. Byte 2 following the sense code contains the subvector key (xx) of the subvector lacking a required subfield, and byte 3 contains the subfield key (xx) of a missing subfield. ΓòÉΓòÉΓòÉ 6.3.32. 086Fxxxx Length Error ΓòÉΓòÉΓòÉ Explanation: A length field within an Management Services (MS) major vector structure is invalid, or two or more length fields are incompatible. The possible values for bytes 2 and 3 are: 0000 0002 xx05 xx06 0007 ΓòÉΓòÉΓòÉ 6.3.32.1. 086F0000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.32.2. 086F0002 ΓòÉΓòÉΓòÉ The sum of the Management Services (MS) subvector lengths is incompatible with the MS major vector length. ΓòÉΓòÉΓòÉ 6.3.32.3. 086Fxx05 ΓòÉΓòÉΓòÉ Management services (MS) subvector length invalid. Byte 2 following the sense code contains the relevant subvector key (xx). (This is specified only if the sum of the subvector lengths is compatible with the major vector length.) ΓòÉΓòÉΓòÉ 6.3.32.4. 086Fxx06 ΓòÉΓòÉΓòÉ Subfield length invalid. Byte 2 following the sense code contains the subvector key (xx) of the Management Services (MS) subvector containing the invalid subfield length. (This is specified only if the sum of the subfield lengths is compatible with the subvector length.) ΓòÉΓòÉΓòÉ 6.3.32.5. 086F0007 ΓòÉΓòÉΓòÉ Invalid or incompatible length fields in an MDS MU. The length field of an MDS MU is incompatible with the sum of the lengths of the imbedded generalized data stream (GDS) variables, or one of the imbedded GDS variables has a length field with a value of less than 4. ΓòÉΓòÉΓòÉ 6.3.33. 0870xxxx Unformatted ΓòÉΓòÉΓòÉ Subvector Value Invalid Explanation: A value in an unformatted Management Services (MS) subvector, or in an unformatted portion of a partially formatted MS subvector, is invalid. The allowed setting for bytes 2 and 3 is: xxxx Byte 2 following the sense code contains the subvector key (xx) of the Management Services (MS) subvector containing the invalid value. Byte 3 contains a 1-byte binary count that indexes the first byte in which the invalid value appears. ΓòÉΓòÉΓòÉ 6.3.34. 0877xxxx Resource Mismatch ΓòÉΓòÉΓòÉ Explanation: The receiver of a request detected a mismatch between two of the following: o The definition of an affected resource o The actual configuration o The definition of the resource as implied in the request The possible values for bytes 2 and 3 are: 002A 002B 002C ΓòÉΓòÉΓòÉ 6.3.34.1. 0877002A ΓòÉΓòÉΓòÉ A session cannot be activated because the node does not support segment generation and the maximum link basic transmission unit (BTU) size is too small to satisfy a requirement on the minimum send RU size as defined for the session mode. ΓòÉΓòÉΓòÉ 6.3.34.2. 0877002B ΓòÉΓòÉΓòÉ A session cannot be activated because the node does not support segment reassembly and the maximum link basic transmission unit (BTU) size is too small to satisfy a requirement on the minimum receive RU size as defined for the session mode. ΓòÉΓòÉΓòÉ 6.3.34.3. 0877002C ΓòÉΓòÉΓòÉ A BFINIT session request was received from a PLU that is not in the same network as this SSCP, or a BFSESSINFO was received reporting a subject LU in another network. ΓòÉΓòÉΓòÉ 6.3.35. 087Dxxxx Session Services Path Error ΓòÉΓòÉΓòÉ Explanation: A session services request cannot be rerouted along a path of SSCP-SSCP sessions. This capability is required, for example, to set up a cross-network LU-LU session. The possible values for bytes 2 and 3 are: 0000 0001 ΓòÉΓòÉΓòÉ 6.3.35.1. 087D0000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.35.2. 087D0001 ΓòÉΓòÉΓòÉ An SSCP has attempted unsuccessfully to reroute a session services request to its destination through one or more adjacent SSCPs; this sense data is sent by a gateway SSCP when it has exhausted trial-and-error rerouting. For example, this sense data is seen when the host is unavailable for a 3270 emulation session. Note: This sense data is used when SSCP rerouting fails completely. The remaining codes are used for failures to reroute to a particular SSCP. For example, they are associated with specific SSCPs when information about a rerouting failure is displayed in the node that was trying to reroute. ΓòÉΓòÉΓòÉ 6.3.36. 0889xxxx Transaction Program Error ΓòÉΓòÉΓòÉ Explanation: The transaction program has detected an error. This sense code is sent only in FMH-7. The possible values for bytes 2 and 3 are: 0000 0001 0100 0101 ΓòÉΓòÉΓòÉ 6.3.36.1. 08890000 ΓòÉΓòÉΓòÉ Either the local side or the remote side issued a SEND_ERROR verb with type(PROG) or an [MC_]SEND_ERROR verb. ΓòÉΓòÉΓòÉ 6.3.36.2. 08890001 ΓòÉΓòÉΓòÉ Program error-Data truncation. The transaction program sending data detected an error and truncated the logical record it was sending. ΓòÉΓòÉΓòÉ 6.3.36.3. 08890100 ΓòÉΓòÉΓòÉ Either the local side or the remote side issued a SEND_ERROR verb with type(SVC). ΓòÉΓòÉΓòÉ 6.3.36.4. 08890101 ΓòÉΓòÉΓòÉ Service transaction program error-Data truncation. The service transaction program sending data detected an error and truncated the logical record it was sending. ΓòÉΓòÉΓòÉ 6.3.37. 088B0000 BB Not Accepted-BIS Reply Requested ΓòÉΓòÉΓòÉ Explanation: Sent in response to a Begin Bracket Request (BB), either an LUSTAT bid or an attach, to indicate that the receiver has sent a BIS request and wants to terminate the session without processing any more conversations, but without sending an UNBIND. A BIS reply is requested so that the negative response sender may send a normal UNBIND. This sense code is sent only by LUs not supporting CNOS protocols. ΓòÉΓòÉΓòÉ 6.3.38. 088Cxxxx Missing Control ΓòÉΓòÉΓòÉ Vector Explanation: The RU or XID did not contain a required control vector. 088Cxxyy Byte 2 contains the key (xx) of the required control vector that is missing. If more than one control vector is missing, only the first omission is reported. Other allowed settings for bytes 2 and 3 are: 0Exx 1000 3200 ΓòÉΓòÉΓòÉ 6.3.38.1. 088C0Exx ΓòÉΓòÉΓòÉ Network Name (X'0E') control vector of type XX missing. ΓòÉΓòÉΓòÉ 6.3.38.2. 088C1000 ΓòÉΓòÉΓòÉ Product Set ID (X'10') control vector missing. ΓòÉΓòÉΓòÉ 6.3.38.3. 088C3200 ΓòÉΓòÉΓòÉ Short-Hold Mode (X'32') control vector missing. ΓòÉΓòÉΓòÉ 6.3.39. 088F0000 XRF Procedure Error ΓòÉΓòÉΓòÉ Explanation: A request was received for an XRF-active or XRF-backup session and was not acted on. ΓòÉΓòÉΓòÉ 6.3.40. 0890xxxx Search Failure ΓòÉΓòÉΓòÉ Explanation: An error occurred while performing a directory search for a resource. The possible values for bytes 2 and 3 are: 0000 0010 0020 0022 0024 0028 0030 0038 0040 0048 0050 0060 0070 0080 ΓòÉΓòÉΓòÉ 6.3.40.1. 08900000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.40.2. 08900010 ΓòÉΓòÉΓòÉ Routing error during a directed search. A Locate generalized data stream (GDS) variable for a directed search was received by an intermediate NNCP and could not be successfully routed to the destination control point. ΓòÉΓòÉΓòÉ 6.3.40.3. 08900020 ΓòÉΓòÉΓòÉ Resource not found during a directed search. A Locate generalized data stream (GDS) variable for a directed search was received by the named destination control point (CP) and the search argument resource is not a local resource. ΓòÉΓòÉΓòÉ 6.3.40.4. 08900022 ΓòÉΓòÉΓòÉ Destination of search not served by this control point (CP). ΓòÉΓòÉΓòÉ 6.3.40.5. 08900024 ΓòÉΓòÉΓòÉ A search request or BIND was received from an unauthorized end node identifying an origin LU not represented in the APPN network node server's directory, and thus could not be authenticated. ΓòÉΓòÉΓòÉ 6.3.40.6. 08900028 ΓòÉΓòÉΓòÉ Resource not found, broadcast required. The resource was not found on a directed locate search, and a restricted broadcast was executed at the destination and failed; a broadcast should be tried. ΓòÉΓòÉΓòÉ 6.3.40.7. 08900030 ΓòÉΓòÉΓòÉ Resource deleted, No broadcast required. A locate generalized data stream (GDS) variable for a directed search was received by the named destination control point (CP) and the search argument resource was deleted. ΓòÉΓòÉΓòÉ 6.3.40.8. 08900038 ΓòÉΓòÉΓòÉ Too many directed search subprocedures. A locate search exceeded the maximum height of the search tree; too many directed search subprocedures were tried; no retry. ΓòÉΓòÉΓòÉ 6.3.40.9. 08900040 ΓòÉΓòÉΓòÉ Resource not found during a broadcast search. A locate generalized data stream (GDS) variable for a broadcast search was received by a control point (CP) that does not provide network services for the search argument resource and neither do any of the CPs searched in its broadcast subtree. This condition is detected by crossing search requests (a CP sends and receives a search request with the same FQPCID and the same search argument resource) or by a local search failure and all CPs in the broadcast subtree returning this sense data. ΓòÉΓòÉΓòÉ 6.3.40.10. 08900048 ΓòÉΓòÉΓòÉ Neutral reply received from an APPN end node. A locate reply with no Found and no Extended Sense Data (X'35') control vector was received from an APPN end node. ΓòÉΓòÉΓòÉ 6.3.40.11. 08900050 ΓòÉΓòÉΓòÉ Quiesced CP. A control point (CP) in the broadcast search tree is in a quiescent state and, therefore, not receiving locate generalized data stream (GDS) variables. This condition is detected when a CP in the search subtree is quiesced and no other CP in the subtree found the requested resource. ΓòÉΓòÉΓòÉ 6.3.40.12. 08900060 ΓòÉΓòÉΓòÉ Storage not available. A control point (CP) in the broadcast search tree does not have sufficient storage to participate in the search and no other CP in the search subtree found the requested resource. ΓòÉΓòÉΓòÉ 6.3.40.13. 08900070 ΓòÉΓòÉΓòÉ Session outage. A control point (CP) in the search tree has lost its CP-CP session with a CP that had been sent a locate generalized data stream (GDS) variable and no reply had been received. ΓòÉΓòÉΓòÉ 6.3.40.14. 08900080 ΓòÉΓòÉΓòÉ Duplicate fully qualified PCID. A control point (CP) in the search tree detected a duplicate fully qualified PCID for a different session request from the session request that first used the fully qualified PCID. ΓòÉΓòÉΓòÉ 6.3.41. 0891xxxx Invalid or Missing Invalid Network ID (NETID) ΓòÉΓòÉΓòÉ Explanation: The network ID is invalid or missing. The possible values for bytes 2 and 3 are: 0004 0005 ΓòÉΓòÉΓòÉ 6.3.41.1. 08910004 ΓòÉΓòÉΓòÉ Indicates that the network name control vector appended to the received XID3 does not contain a valid network ID. The network ID, preceding the control point (CP) name, must be greater than 0 and less than 8 bytes in length. ΓòÉΓòÉΓòÉ 6.3.41.2. 08910005 ΓòÉΓòÉΓòÉ Invalid control point (CP) name in the network name (X'0E', CP name) control vector. ΓòÉΓòÉΓòÉ 6.3.42. 0895xxxx Control Vector Error ΓòÉΓòÉΓòÉ Explanation: The RU or XID contained a control vector that was in error. Byte 2 (xx) contains the key of the control vector first detected in error. If more than one control vector is in error, only the first erroneous one is reported. Byte 3 (xx) of the sense code specific data contains the (0-origin) byte offset of the error within the control vector. Another possible value for bytes 2 and 3 is: 0000 ΓòÉΓòÉΓòÉ 6.3.42.1. 08950000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.3.43. 0897xxxx System Definition Mismatch ΓòÉΓòÉΓòÉ Explanation: The requested function is not supported by the receiver, or there is a mismatch between the sending and receiving system definitions. The possible values for bytes 2 and 3 are: 000D 0011 ΓòÉΓòÉΓòÉ 6.3.43.1. 0897000D ΓòÉΓòÉΓòÉ Resource type not defined in receiver. ΓòÉΓòÉΓòÉ 6.3.43.2. 08970011 ΓòÉΓòÉΓòÉ An APPN end node does not support locate. CP-CP sessions are being unbound because the adjacent node indicated that it does support CP-CP sessions but does not support receipt of LOCATE/CDINIT search requests. ΓòÉΓòÉΓòÉ 6.3.44. 08980003 XRF-active Hierarchical Reset ΓòÉΓòÉΓòÉ Explanation: The XRF session is being reset. X'0003' indicates that the identified XRF-active LU-LU session is being deactivated because the related XRF-backup session performed a forced takeover of this session (through SWITCH). The LU sending this sense data is resetting its half-session before receiving the response from the partner LU. (See UNBIND type X'13'.) ΓòÉΓòÉΓòÉ 6.3.45. 08A0xxxx Session Reset ΓòÉΓòÉΓòÉ Explanation: An LU or PU is resetting an LU-LU session. The possible values for bytes 2 and 3 are: 0002 0004 0005 0006 ΓòÉΓòÉΓòÉ 6.3.45.1. 08A00002 ΓòÉΓòÉΓòÉ The LU or SCM is sending UNBIND with a reason code of X'0F' (cleanup). ΓòÉΓòÉΓòÉ 6.3.45.2. 08A00004 ΓòÉΓòÉΓòÉ Reversed FRSN values. The control point (CP) is sending an UNBIND with a reason code of X'0F' (cleanup); the value in the Last FRSN Sent field is greater than the value in the Current FRSN field (no retry). ΓòÉΓòÉΓòÉ 6.3.45.3. 08A00005 ΓòÉΓòÉΓòÉ Topology Database Update (TDU) sent out of order. The control point (CP) is sending an UNBIND with a reason code of X'0F' (cleanup); the value in the Last FRSN Sent field of the current TDU generalized data stream (GDS) variable is not equal to the value of the Current FRSN field in the TDU generalized data stream (GDS) variable that immediately preceded it (no retry). ΓòÉΓòÉΓòÉ 6.3.45.4. 08A00006 ΓòÉΓòÉΓòÉ Invalid FRSN value. In CP Capabilities, the adjacent node indicated receipt of a Topology Database Update (TDU) with a FRSN value greater than the last one sent. ΓòÉΓòÉΓòÉ 6.3.46. 08A8xxxx Multiple-Domain Support Routing Exception ΓòÉΓòÉΓòÉ Explanation: The MDS router in the reporting network accessible unit (NAU) is unable to perform the required routing for an MDS MU. When this SNA report code is used in an SNA condition report (X'1532') generalized data stream (GDS) variable, the destination NAU name is included in the Reported on Location Name (X'09') subvector and the destination management services (MS) application name is included in the Reported On Agent (X'04') subvector of the condition report. The possible values for bytes 2 and 3 are: 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B 000C 000D 000E 000F ΓòÉΓòÉΓòÉ 6.3.46.1. 08A80001 ΓòÉΓòÉΓòÉ Destination NAU name unknown. Directory services could not locate the requested destination name. ΓòÉΓòÉΓòÉ 6.3.46.2. 08A80002 ΓòÉΓòÉΓòÉ Directory services unavailable. No routing possible. ΓòÉΓòÉΓòÉ 6.3.46.3. 08A80003 ΓòÉΓòÉΓòÉ Management services (MS) application name not recognized. ΓòÉΓòÉΓòÉ 6.3.46.4. 08A80004 ΓòÉΓòÉΓòÉ Use of the CPSVCMG session not permitted. The reporting APPN network node has received an MDS MU over a CPSVCMG session from another network node. These sessions are used for MDS MUs only between an APPN network node and its served APPN end nodes. ΓòÉΓòÉΓòÉ 6.3.46.5. 08A80005 ΓòÉΓòÉΓòÉ Function not supported by the end node destination. The APPN end node destination does not support receipt of management services (MS) messages (reported by serving the APPN network node). ΓòÉΓòÉΓòÉ 6.3.46.6. 08A80006 ΓòÉΓòÉΓòÉ Function not supported by APPN network node destination. The APPN network node destination does not support receipt of management services (MS) messages other than MS Capabilities and alerts (reported by the APPN network node performing routing). ΓòÉΓòÉΓòÉ 6.3.46.7. 08A80007 ΓòÉΓòÉΓòÉ Function not supported by serving APPN network node. The serving network node of the APPN end node destination does not support routing of management services (MS) messages (reported by the APPN network node performing routing). ΓòÉΓòÉΓòÉ 6.3.46.8. 08A80008 ΓòÉΓòÉΓòÉ Function not supported by the end node. The reporting APPN end node has received an MDS MU with a destination other than itself. ΓòÉΓòÉΓòÉ 6.3.46.9. 08A80009 ΓòÉΓòÉΓòÉ Destination not supported by reporting APPN network node. An APPN network node has received an MDS MU from another network node that cannot be routed. The destination is not the reporting network node itself nor is it one of the served APPN end nodes. If the MDS MU was routed based on unverified directory information (as indicated by the Routing verification indicator in the MDS Routing Information), the MDS MU is returned to the routing APPN network node along with the SNA condition report. ΓòÉΓòÉΓòÉ 6.3.46.10. 08A8000A ΓòÉΓòÉΓòÉ Unrecoverable session failure. The MDS_SEND TP in the reporting node was unable to send the message because of an allocation error. Retries have been exhausted. ΓòÉΓòÉΓòÉ 6.3.46.11. 08A8000B ΓòÉΓòÉΓòÉ Unrecoverable TP failure in remote node. The MDS_SEND TP in the reporting node was unable to send the message because of a TP failure in a remote node. Retries have been exhausted. ΓòÉΓòÉΓòÉ 6.3.46.12. 08A8000C ΓòÉΓòÉΓòÉ Management services (MS) application failure. The MDS router in the destination NAU is unable to communicate with the destination management services (MS) application program. ΓòÉΓòÉΓòÉ 6.3.46.13. 08A8000D ΓòÉΓòÉΓòÉ Unrecoverable TP failure in reporting node. The MDS router in the reporting node was unable to send the message because of a local TP failure. ΓòÉΓòÉΓòÉ 6.3.46.14. 08A8000E ΓòÉΓòÉΓòÉ Correlation error. An MDS MU has been received that is not the first for a unit of work (First MDS Message indicator in the MDS Routing Information Message is OFF), but the unit of work correlator is unknown (does not match any active MDS transaction). ΓòÉΓòÉΓòÉ 6.3.46.15. 08A8000F ΓòÉΓòÉΓòÉ Management services (MS) application congestion. The MDS router in the destination NAU is unable to communicate with the destination management services (MS) application because of local congestion (implementation buffer space for queuing additional MDS MUs has been exhausted). ΓòÉΓòÉΓòÉ 6.3.47. 08A9xxxx Multiple-Domain Support Transaction Failure ΓòÉΓòÉΓòÉ Explanation: The reporting MDS router or management services (MS) application has detected a condition that has impacted an outstanding unit of work (identified by the unit-of-work correlator of the MDS error message) or MDS MU. The possible values for bytes 2 and 3 are: 0001 0002 0003 0004 0005 0007 ΓòÉΓòÉΓòÉ 6.3.47.1. 08A90001 ΓòÉΓòÉΓòÉ Failure caused by outage of a CPSVCMG session. ΓòÉΓòÉΓòÉ 6.3.47.2. 08A90002 ΓòÉΓòÉΓòÉ Failure caused by outage of an SNASVCMG session. All retries have been exhausted. ΓòÉΓòÉΓòÉ 6.3.47.3. 08A90003 ΓòÉΓòÉΓòÉ Unit of work canceled by reporting management services (MS) application program. The unit of work was canceled because of a time-out in the reporting management services (MS) application program. ΓòÉΓòÉΓòÉ 6.3.47.4. 08A90004 ΓòÉΓòÉΓòÉ Unit of work canceled by reporting MDS Router. The unit of work was canceled by a garbage-collection time-out in the reporting MDS router. ΓòÉΓòÉΓòÉ 6.3.47.5. 08A90005 ΓòÉΓòÉΓòÉ MDS router internal failure. The unit of work was canceled because of an internal failure in the reporting MDS router. ΓòÉΓòÉΓòÉ 6.3.47.6. 08A90007 ΓòÉΓòÉΓòÉ Unit of work was canceled because an MS application issued the UNREGISTER_MS_APPLICATION verb or the application program ended while the unit of work was active. The application was either the origin or destination MS application for the unit of work. ΓòÉΓòÉΓòÉ 6.3.48. 08AAxxxx Required GDS Variable Missing ΓòÉΓòÉΓòÉ Explanation: The Management Services (MS) MDS MU is missing a required generalized data stream (GDS) variable. The allowed setting for bytes 2 and 3 is: xxxx Bytes 2 and 3 following the sense code contain the ID of the missing GDS variable. ΓòÉΓòÉΓòÉ 6.3.49. 08B50000 Network Node Server Not Required ΓòÉΓòÉΓòÉ Explanation: This sense code is sent by an APPN end node control point to deactivate CP-CP sessions with the NNCP, or to reject a CP-CP session BIND request from the NNCP. The APPN end node no longer requires APPN network node services from the receiver. Note: This sense code is carried within the CV X'35' portion of the UNBIND request. ΓòÉΓòÉΓòÉ 6.4. X'10' Request Error ΓòÉΓòÉΓòÉ This category indicates that the RU was delivered to the intended network accessible unit (NAU) component, but could not be interpreted or processed. This condition represents a mismatch of NAU capabilities. Select a sense code for specific information. 1001xxxx RU Data Error 10020000 RU Length Error 1003xxxx Function Not Supported 10050000 Parameter Error 10070000 Category Not Supported 1008xxxx Invalid FM Header 1010xxxx Error on Locate Search or CP Capabilities Message Detected 1014xxxx Control Vector Error on a Directory Services GDS Variable 1015xxxx XID Length Error 1016xxxx XID Format 3 Parameter Error 101A0000 Invalid Control Vector Sequence ΓòÉΓòÉΓòÉ 6.4.1. 1001xxxx RU Data Error ΓòÉΓòÉΓòÉ Explanation: Data in the request RU is not acceptable to the receiving component. For example, a character code is not in the set supported, a formatted data field is not acceptable to presentation services, or a value specified in the length field (LL) of a structured field is invalid. The possible values for bytes 2 and 3 are: 0000 0003 0024 0025 ΓòÉΓòÉΓòÉ 6.4.1.1. 10010000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.4.1.2. 10010003 ΓòÉΓòÉΓòÉ Isolated pacing message (IPM) format error. An incorrectly formatted IPM was received. ΓòÉΓòÉΓòÉ 6.4.1.3. 10010024 ΓòÉΓòÉΓòÉ A BIND was received that was not for LU 6.2 and not in extended format. The BIND is rejected. ΓòÉΓòÉΓòÉ 6.4.1.4. 10010025 ΓòÉΓòÉΓòÉ Unable to extend BIND request. An attempt made to add control vectors to a BIND request would have exceeded the maximum BIND length. The BIND is rejected. ΓòÉΓòÉΓòÉ 6.4.2. 10020000 RU Length Error ΓòÉΓòÉΓòÉ Explanation: The request RU was too long or too short. ΓòÉΓòÉΓòÉ 6.4.3. 1003xxxx Function Not Supported ΓòÉΓòÉΓòÉ Explanation: The function requested is not supported. The function may have been specified by a formatted request code, a field in an RU, or a control character. The possible values for bytes 2 and 3 are: 0000 000D 0014 0021 0022 ΓòÉΓòÉΓòÉ 6.4.3.1. 10030000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.4.3.2. 1003000D ΓòÉΓòÉΓòÉ The function identified in the request is not supported by the processing application transaction program. ΓòÉΓòÉΓòÉ 6.4.3.3. 10030014 ΓòÉΓòÉΓòÉ Cryptography is not supported, but a nonzero length was specified for the cryptography key. ΓòÉΓòÉΓòÉ 6.4.3.4. 10030021 ΓòÉΓòÉΓòÉ There is a mismatch between the session initiation request type and the LU type (independent or dependent). The most probable cause is an LU defined in your OS/2 node as an independent LU that is incorrectly defined as a dependent LU in the subarea node. There are other causes, but in every case, the cause involves a "session initiation type mismatch". Your LU used dependent LU session initiation protocols (ACTLU, INIT_SELF) and the partner was expecting independent LU protocols, or your LU used independent LU session initiation protocols (BIND) and the partner expected dependent LU protocols. ΓòÉΓòÉΓòÉ 6.4.3.5. 10030022 ΓòÉΓòÉΓòÉ The BIND was received by an APPN end node, which is not a destination. A BIND was received that contained an Route Selection control vector (RSCV) specifying a destination other than this node. As this node is configured as an APPN end node, the BIND is rejected. ΓòÉΓòÉΓòÉ 6.4.4. 10050000 Parameter Error ΓòÉΓòÉΓòÉ Explanation: A parameter modifying a control function is invalid or outside the range allowed by the receiver. ΓòÉΓòÉΓòÉ 6.4.5. 10070000 Category Not Supported ΓòÉΓòÉΓòÉ Explanation: DFC, SC, NC, or FMD request was received by a half-session not supporting any requests in that category, an NS request byte 0 was not set to a defined value, or byte 1 was not set to an NS category supported by the receiver. ΓòÉΓòÉΓòÉ 6.4.6. 1008xxxx Invalid FM Header ΓòÉΓòÉΓòÉ Explanation: The FM header was not understood or translatable by the receiver, or an FM header was expected but not present. For LU 6.2, this sense code is sent in FMH-7 or UNBIND. The possible values for bytes 2 and 3 are: 200E 201D 4001 6000 6005 6009 600B 6011 6021 6031 6032 6034 6040 6041 6042 6043 6044 ΓòÉΓòÉΓòÉ 6.4.6.1. 1008200E ΓòÉΓòÉΓòÉ Invalid concatenation indicator. The concatenation indicator is on, but concatenation is not allowed. ΓòÉΓòÉΓòÉ 6.4.6.2. 1008201D ΓòÉΓòÉΓòÉ FM header and associated data mismatch. The FM header indicated associated data would or would not follow (for example, FM header 7 followed by log data, or FM header 5 followed by program initialization parameters), but this indication was in error; or a previously received RU (for example, -RSP(X'0846')) implied that an FM header would follow, but none was received. ΓòÉΓòÉΓòÉ 6.4.6.3. 10084001 ΓòÉΓòÉΓòÉ Invalid FM header type for this LU. The type of the FM header is other than 5, 7, or 12. ΓòÉΓòÉΓòÉ 6.4.6.4. 10086000 ΓòÉΓòÉΓòÉ FM header length not correct. The value in the FM header Length field differs from the sum of the lengths of the subfields of the FM header. ΓòÉΓòÉΓòÉ 6.4.6.5. 10086005 ΓòÉΓòÉΓòÉ Access security information length field not correct. The value in the Access Security Information Length field differs from the sum of the lengths of the Access Security Information subfields. ΓòÉΓòÉΓòÉ 6.4.6.6. 10086009 ΓòÉΓòÉΓòÉ Invalid parameter length. The field that specifies the length of fixed-length parameters has an invalid setting. ΓòÉΓòÉΓòÉ 6.4.6.7. 1008600B ΓòÉΓòÉΓòÉ Unrecognized FM header command code. The partner LU received an FM header command code that it does not recognize. For LU 6.2 this sense data is sent only in FMH-7. ΓòÉΓòÉΓòÉ 6.4.6.8. 10086011 ΓòÉΓòÉΓòÉ Invalid logical unit of work (LUW). The LUW Length field (in a Compare States generalized data stream (GDS) variable or an FMH-5) is incorrect, or the length field is invalid, or an LUW ID is not present but is required by the setting of the synchronization level field. ΓòÉΓòÉΓòÉ 6.4.6.9. 10086021 ΓòÉΓòÉΓòÉ Transaction program name not recognized. The FMH-5 attach command specifies a transaction program name that the receiver does not recognize. This sense data is sent only in FMH-7. The partner LU rejected the incoming attach because the local transaction program specified a tp_name that the partner LU does not recognize. This sense data can also indicate that the partner LU recognized the TP name, but could not start the program. One reason for this may be authorization problems. Some implementations of APPC (such as VM) check that three things match up: LU name, mode name, and TP name. These machines check the incoming user_id and password of each specific TP, and reject the attach with this sense data if your program is not authorized to start the corresponding program on the remote machine. Possible reasons for this error are : o If the remote location is using Communications Manager, its TP definition may have the TP name spelled wrong or be using the wrong combination of uppercase and lowercase characters. The TP name configured at the remote location must exactly match the tp_name you specified on the [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb in your local OS/2 program. The TP name field in the TP definition is one of the few APPC configuration fields that is case sensitive. Be sure that the combination of uppercase and lowercase letters matches those specified in the program. o If the remote location is running the VM operating system, this sense data is received if the remote VM AVS is not authorized through the *IDENT control statements in VM to send information to the TP. This sense data is saying that there is no way to get to the TP on VM from the OS/2 program. o If the remote location is running the VM operating system and is configured as a gateway, then it should be configured as a private gateway and not a public gateway. APPC wrote an error log entry of major error code 0001, minor error code 10086021 to the error log in the local workstation. Programmer Response: Check the validity of the TP name and the designated partner LU and mode names. Operator Response: On the remote machine, check the list of TP names to be recognized. Ensure that they match the values supplied for the tp_name values on the [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verbs in the local workstation. If you find the TP correctly defined on the remote machine, ensure that remote TP is properly authorized for the user_id and password sent on the attach. ΓòÉΓòÉΓòÉ 6.4.6.10. 10086031 ΓòÉΓòÉΓòÉ PIP not allowed. The FMH-5 attach command specifies program initialization parameter (PIP) data is present, but the receiver does not support PIP data for the specified transaction program. This sense data is sent only in FMH-7. The partner LU rejected the attach because the local transaction program specified program initialization parameters (PIP data); either the partner LU does not support PIP data or the partner transaction program has no PIP variables defined. APPC reports this sense data on an [MC_]SEND_CONVERSATION verb or on a conversation verb issued after the [MC_]ALLOCATE verb. APPC wrote an error log entry of major error code 0001, minor error code 10086031 to the error log in the local workstation. Programmer Response: Do not use PIP data when communicating with this remote transaction program. For example, Communications Manager APPC does not accept incoming PIP data. ΓòÉΓòÉΓòÉ 6.4.6.11. 10086032 ΓòÉΓòÉΓòÉ PIP Not Specified Correctly. The FMH-5 attach command specifies a transaction program name that requires program initialization parameter (PIP) data, and either the FMH-5 specifies PIP data is not present or the number of PIP subfields present does not agree with the number required for the program. This sense data is sent only in FMH-7. The partner LU rejected the incoming attach because the partner transaction program has one or more PIP variables defined and either the local transaction program has specified that no PIP variables are to be used, or the number of PIP variables defined by the local transaction program is different from the number specified by the remote transaction program. APPC wrote an error log entry of major error code 0001, minor error code 10086032 to the error log in the local workstation. Programmer Response: Specify that PIP data is to be used in the [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb, and make sure that the number of PIP variables agrees with the number required by the remote transaction program. ΓòÉΓòÉΓòÉ 6.4.6.12. 10086034 ΓòÉΓòÉΓòÉ Conversation type mismatch. The FMH-5 attach command specifies a conversation type that the receiver does not support for the specified transaction program. This sense data is sent only in FMH-7. The partner LU rejected the incoming attach because it or the partner transaction program does not support the specified conversation type. APPC wrote an error log entry of major error code 0001, minor error code 10086034 to the error log in the local workstation. Programmer Response: Change the transaction program so it uses the proper conversation type (basic or mapped). Operator Response: Change the TP definition at the partner to reflect the conversation type used by the program. ΓòÉΓòÉΓòÉ 6.4.6.13. 10086040 ΓòÉΓòÉΓòÉ Invalid attach parameter. A parameter in the FMH-5 attach command conflicts with the statement of LU capability previously provided in the BIND negotiation. ΓòÉΓòÉΓòÉ 6.4.6.14. 10086041 ΓòÉΓòÉΓòÉ Synchronization level not supported. The FMH-5 attach command specifies a synchronization level that the receiver does not support for the specified transaction program. This sense data is sent only in FMH-7. The partner LU rejected the incoming attach because the local transaction program specified an unacceptable sync_level parameter. For example, the local transaction program issued an ALLOCATE verb with sync_level(CONFIRM), but at the remote machine it was configured as sync_level(NONE). APPC wrote an error log entry of major error code 0001, minor error code 10086041 to the error log in the local workstation. Programmer Response: Change the sync_level parameter on the [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb. Operator Response: Change the TP definition at the partner to reflect the sync_level used by the local transaction program. ΓòÉΓòÉΓòÉ 6.4.6.15. 10086042 ΓòÉΓòÉΓòÉ Reconnection not supported. FMH-5 attach command specifies reconnection support but the receiver does not support reconnection for the specified transaction program. This sense data is sent only in FMH-7. ΓòÉΓòÉΓòÉ 6.4.6.16. 10086043 ΓòÉΓòÉΓòÉ Unable to reconnect transaction program-No retry. The FMH-5 Reconnect command specifies the conversation correlator of a transaction program to which the receiver cannot reconnect. The condition is not temporary. This sense data is sent only in FMH-7. ΓòÉΓòÉΓòÉ 6.4.6.17. 10086044 ΓòÉΓòÉΓòÉ Unable to reconnect transaction program-Retry allowed. The FMH-5 Reconnect command specifies the conversation correlator of a transaction program to which the receiver cannot reconnect. The condition is temporary. This sense data is sent only in FMH-7. ΓòÉΓòÉΓòÉ 6.4.7. 1010xxxx Error on locate search or CP Capabilities Message Detected ΓòÉΓòÉΓòÉ Explanation: An error was detected during directory search or CP Capabilities exchange processing. The possible values for bytes 2 and 3 are: 0000 1000 1002 4004 5002 5006 A002 B080 ΓòÉΓòÉΓòÉ 6.4.7.1. 10100000 ΓòÉΓòÉΓòÉ Unrecoverable error, such as a duplicate control vector, was detected. ΓòÉΓòÉΓòÉ 6.4.7.2. 10101000 ΓòÉΓòÉΓòÉ Length error in CP Capabilities generalized data stream (GDS) variable. ΓòÉΓòÉΓòÉ 6.4.7.3. 10101002 ΓòÉΓòÉΓòÉ Identifier error in CP Capabilities GDS variable. ΓòÉΓòÉΓòÉ 6.4.7.4. 10104004 ΓòÉΓòÉΓòÉ Incomplete negative or neutral reply received on a search, or reservation indicated on broadcast, or All specified on a directed search. ΓòÉΓòÉΓòÉ 6.4.7.5. 10105002 ΓòÉΓòÉΓòÉ No CDINIT generalized data stream (GDS) variable returned on a search request. ΓòÉΓòÉΓòÉ 6.4.7.6. 10105006 ΓòÉΓòÉΓòÉ Session polarity or initiate type value received in CDINIT generalized data stream (GDS) variable not supported. ΓòÉΓòÉΓòÉ 6.4.7.7. 1010A002 ΓòÉΓòÉΓòÉ Find generalized data stream (GDS) variable not present on locate search request. ΓòÉΓòÉΓòÉ 6.4.7.8. 1010B080 ΓòÉΓòÉΓòÉ Command Parameters (X'80') control vector not present on Found generalized data stream (GDS) variable. ΓòÉΓòÉΓòÉ 6.4.8. 1014xxxx Control Vector Error on a Directory Services GDS Variable ΓòÉΓòÉΓòÉ Explanation: An error was detected on one of the following generalized data stream (GDS) variables: Locate, Find, Found, CDINIT, Register, or Delete. The possible values for bytes 2 and 3 are: 003C 003D 0080 023C 502B 502C 5046 A082 B280 ΓòÉΓòÉΓòÉ 6.4.8.1. 1014003C ΓòÉΓòÉΓòÉ Missing Associated Resource Entry (X'3C') control vector. ΓòÉΓòÉΓòÉ 6.4.8.2. 1014003D ΓòÉΓòÉΓòÉ Missing Directory Entry (X'3D') control vector. ΓòÉΓòÉΓòÉ 6.4.8.3. 10140080 ΓòÉΓòÉΓòÉ Invalid control vector. ΓòÉΓòÉΓòÉ 6.4.8.4. 1014023C ΓòÉΓòÉΓòÉ Conflicting directory entry or invalid Associated Resource Entry (X'3C') control vector. ΓòÉΓòÉΓòÉ 6.4.8.5. 1014502B ΓòÉΓòÉΓòÉ No Route Selection control vector (RSCV) was received from an APPN network node server. ΓòÉΓòÉΓòÉ 6.4.8.6. 1014502C ΓòÉΓòÉΓòÉ No COS/TPF control vector received from an APPN network node server. ΓòÉΓòÉΓòÉ 6.4.8.7. 10145046 ΓòÉΓòÉΓòÉ TG vectors not present in a CDINIT from an APPN end node OLU or DLU. ΓòÉΓòÉΓòÉ 6.4.8.8. 1014A082 ΓòÉΓòÉΓòÉ Missing Search Argument Directory Entry (X'82') control vector on Find. ΓòÉΓòÉΓòÉ 6.4.8.9. 1014B280 ΓòÉΓòÉΓòÉ A Found from an APPN end node indicated the directory entry for a located resource was a wildcard entry. ΓòÉΓòÉΓòÉ 6.4.9. 1015xxxx XID Length Error ΓòÉΓòÉΓòÉ Explanation: The XID3 was too long or too short. The possible values for bytes 2 and 3 are: 0001 0002 ΓòÉΓòÉΓòÉ 6.4.9.1. 10150001 ΓòÉΓòÉΓòÉ Too few bytes in XID3. ΓòÉΓòÉΓòÉ 6.4.9.2. 10150002 ΓòÉΓòÉΓòÉ Indicates a mismatch between the number of bytes specified in the Length field of XID3 and the actual length of the received XID3. ΓòÉΓòÉΓòÉ 6.4.10. 1016xxxx XID Format 3 Parameter Error ΓòÉΓòÉΓòÉ Explanation: Data in the XID3 is not acceptable to the receiving component because the value in the received XID3 field, whose byte and bit offset is specified by the XID Negotiation Error (X'22') control vector (which also carries this sense code), is inconsistent with the corresponding field in the sent XID3. The possible values for bytes 2 and 3 are: 0001 0002 0003 0004 0005 0006 0007 0009 000A 000B 000F 0010 0017 001B 001C ΓòÉΓòÉΓòÉ 6.4.10.1. 10160001 ΓòÉΓòÉΓòÉ The field in the received XID3 that specifies the maximum number of I frames that the sender can receive before acknowledgment is set to 0. ΓòÉΓòÉΓòÉ 6.4.10.2. 10160002 ΓòÉΓòÉΓòÉ The adjacent node has been inconsistent in its request for ACTPU. In a nonactivation XID3 exchange, it has changed the value of the ACTPU Suppression indicator sent in the previous XID3 exchange. ΓòÉΓòÉΓòÉ 6.4.10.3. 10160003 ΓòÉΓòÉΓòÉ The field in the received XID3 that specifies the maximum basic transmission unit (BTU) length that the sender can receive is set less than 99 bytes, the minimum required. ΓòÉΓòÉΓòÉ 6.4.10.4. 10160004 ΓòÉΓòÉΓòÉ The received XID was not XID format 3 when XID format 3 was expected. ΓòÉΓòÉΓòÉ 6.4.10.5. 10160005 ΓòÉΓòÉΓòÉ The adjacent node does not support BIND segment generation but does support receipt of BIND segments. Any T2.1 node supporting receipt of BIND segments must also support generation of BIND segments. ΓòÉΓòÉΓòÉ 6.4.10.6. 10160006 ΓòÉΓòÉΓòÉ The adjacent node is an APPN end node, does not support BIND segment receipt, and has a maximum basic transmission unit (BTU) size of less than 265, the minimum required here. ΓòÉΓòÉΓòÉ 6.4.10.7. 10160007 ΓòÉΓòÉΓòÉ The adjacent node is an APPN network node, does not support BIND segment receipt, and has a maximum basic transmission unit (BTU) size of less than 521, the minimum size required here. ΓòÉΓòÉΓòÉ 6.4.10.8. 10160009 ΓòÉΓòÉΓòÉ The adjacent node is an APPN network node, does not provide control point (CP) services, and supports CP-CP sessions, a combination not allowed. ΓòÉΓòÉΓòÉ 6.4.10.9. 1016000A ΓòÉΓòÉΓòÉ During a nonactivation XID exchange the adjacent node has changed the TG number that was negotiated during the activation exchange. ΓòÉΓòÉΓòÉ 6.4.10.10. 1016000B ΓòÉΓòÉΓòÉ The adjacent node is the TG number negotiation winner and designates a TG number that the receiving node cannot allocate to this connection. Possible reasons for this error are: o The TG negotiation winner designates 0 as the TG number when parallel TGs are supported. o The TG negotiation winner designates 0 as the TG number that is already in use because of an active connection to another node. This can occur when two nodes with identical fully qualified CP names try to connect to the same node. ΓòÉΓòÉΓòÉ 6.4.10.11. 1016000F ΓòÉΓòÉΓòÉ The link station roles specified in the sent and received negotiation-proceeding XID3s are not compatible. To activate a connection, one node must contain a primary link station; the other, a secondary link station. ΓòÉΓòÉΓòÉ 6.4.10.12. 10160010 ΓòÉΓòÉΓòÉ The support of combined asynchronous balanced mode link stations indicated in the sent and received negotiation-proceeding XID3s is not in agreement. ΓòÉΓòÉΓòÉ 6.4.10.13. 10160017 ΓòÉΓòÉΓòÉ After two negotiation proceeding XID exchanges, two negotiable link stations still have equal values in the Node Identification fields of their XID3s. ΓòÉΓòÉΓòÉ 6.4.10.14. 1016001B ΓòÉΓòÉΓòÉ The adjacent node is an APPN node but does not support adaptive BIND pacing as a sender and receiver. ΓòÉΓòÉΓòÉ 6.4.10.15. 1016001C ΓòÉΓòÉΓòÉ The adjacent node sends a reserved value in the XID3 field defining its link station role. ΓòÉΓòÉΓòÉ 6.4.11. 101A0000 Invalid Control Vector Sequence ΓòÉΓòÉΓòÉ Explanation: A control vector was found containing a key that was invalid for the position of the control vector within a Topology Database Update (TDU). ΓòÉΓòÉΓòÉ 6.5. X'20' State Error ΓòÉΓòÉΓòÉ This category indicates a sequence number error or an RH or RU that it is not allowed for the receiver's current session control or data flow control state. These errors prevent delivery of the request to the intended component. Select a sense code for specific information. 20010000 Sequence Number 20020000 Chaining 20030000 Bracket 20040000 Direction 20080000 No Begin Bracket 200A0000 Immediate Request Mode Error 200E0000 Response Correlation Error 20100000 BIS Protocol Error 2011xxxx Pacing Protocol Error 20120000 Invalid Sense Code Received ΓòÉΓòÉΓòÉ 6.5.1. 20010000 Sequence Number ΓòÉΓòÉΓòÉ Explanation: Sequence number received on normal-flow request was not 1 greater than the last. ΓòÉΓòÉΓòÉ 6.5.2. 20020000 Chaining ΓòÉΓòÉΓòÉ Explanation: Error in the sequence of the chain indicator settings (BCI, ECI), such as first, middle, first. ΓòÉΓòÉΓòÉ 6.5.3. 20030000 Bracket ΓòÉΓòÉΓòÉ Explanation: Error resulting from failure of sender to enforce bracket rules for session. (This error does not apply to contention or race conditions.) ΓòÉΓòÉΓòÉ 6.5.4. 20040000 Direction ΓòÉΓòÉΓòÉ Explanation: Error resulting from a normal-flow request received while the half-duplex flip-flop state was not Receive. ΓòÉΓòÉΓòÉ 6.5.5. 20080000 No Begin Bracket ΓòÉΓòÉΓòÉ Explanation: An FMD request specifying BBI=BB was received after the receiver had previously received a Bracket Initiation Stopped request. ΓòÉΓòÉΓòÉ 6.5.6. 200A0000 Immediate Request Mode Error ΓòÉΓòÉΓòÉ Explanation: The immediate request mode protocol has been violated by the request. ΓòÉΓòÉΓòÉ 6.5.7. 200E0000 Response Correlation Error ΓòÉΓòÉΓòÉ Explanation: A response was received that cannot be correlated to a previously sent request. ΓòÉΓòÉΓòÉ 6.5.8. 20100000 BIS Protocol Error ΓòÉΓòÉΓòÉ Explanation: A BIS protocol error was detected; for example, a BIS request was received after a previous BIS was received and processed. ΓòÉΓòÉΓòÉ 6.5.9. 2011xxxx Pacing Protocol Error ΓòÉΓòÉΓòÉ Explanation: A violation of pacing protocols was detected. The possible values for bytes 2 and 3 are: 0000 0001 0002 0003 ΓòÉΓòÉΓòÉ 6.5.9.1. 20110000 ΓòÉΓòÉΓòÉ A normal-flow or BIND request was received after the pacing count had been reduced to 0 and before a pacing response had been sent. ΓòÉΓòÉΓòÉ 6.5.9.2. 20110001 ΓòÉΓòÉΓòÉ Unexpected isolated pacing message (IPM) received. An IPM was received when the receiver was in a state that did not allow it. ΓòÉΓòÉΓòÉ 6.5.9.3. 20110002 ΓòÉΓòÉΓòÉ Unexpected pacing request received. A request with the pacing indicator set was received when the receiver was in a state that did not allow it. ΓòÉΓòÉΓòÉ 6.5.9.4. 20110003 ΓòÉΓòÉΓòÉ Pacing Response Indicator incorrectly set. The pacing indicator was set in a non-IPM response received while adaptive pacing was being used. ΓòÉΓòÉΓòÉ 6.5.10. 20120000 Invalid Sense Code Received ΓòÉΓòÉΓòÉ Explanation: A negative response was received that contains an SNA-defined sense code that cannot be used for the sent request. ΓòÉΓòÉΓòÉ 6.6. X'40' RH Usage Error ΓòÉΓòÉΓòÉ This category indicates that the value of a field or combination of fields in the RH violates architectural rules or previously selected BIND options. These errors prevent delivery of the request to the intended component and are independent of the current states of the session. They may result from the failure of the sender to enforce session rules. Detection by the receiver of each of these errors is optional. Select a sense code for specific information. 40030000 BB Not Allowed 40070000 Definite Response Not Allowed 40110000 Incorrect Specification of RU Category 40120000 Incorrect Specification of Request Code 40130000 Incorrect Specification of (SDI, RTI) 40140000 Incorrect Use of (DR1I, DR2I, ERI) 40150000 Incorrect Use of QRI 40190000 Incorrect Indicators with Last-In-Chain Request ΓòÉΓòÉΓòÉ 6.6.1. 40030000 BB Not Allowed ΓòÉΓòÉΓòÉ Explanation: The Begin Bracket indicator (BBI) was specified incorrectly; for example, BBI=BB with BCI=╨║BC. ΓòÉΓòÉΓòÉ 6.6.2. 40070000 Definite Response Not Allowed ΓòÉΓòÉΓòÉ Explanation: Definite response was requested when not permitted. ΓòÉΓòÉΓòÉ 6.6.3. 40110000 Incorrect Specification of RU Category ΓòÉΓòÉΓòÉ Explanation: The RU Category indicator was specified incorrectly; for example, an expedited-flow request or response was specified with RU Category indicator = FMD. ΓòÉΓòÉΓòÉ 6.6.4. 40120000 Incorrect Specification of Request Code ΓòÉΓòÉΓòÉ Explanation: The request code on a response does not match the request code on its corresponding request. ΓòÉΓòÉΓòÉ 6.6.5. 40130000 Incorrect Specification of (SDI, RTI) ΓòÉΓòÉΓòÉ Explanation: The Sense Data Included indicator (SDI) and the Response Type indicator (RTI) were not specified properly on a response. The proper value pairs are (SDI=SD, RTI=negative) and (SDI=╨║SD, RTI=positive). ΓòÉΓòÉΓòÉ 6.6.6. 40140000 Incorrect Use of (DR1I, DR2I, ERI) ΓòÉΓòÉΓòÉ Explanation: The Definite Response 1 indicator (DR1I), Definite Response 2 indicator (DR2I), and Exception Response indicator (ERI) were specified incorrectly; for example, a SIGNAL request was not specified with DR1I=DR1, DR2I=╨║DR2, and ERI=╨║ER. ΓòÉΓòÉΓòÉ 6.6.7. 40150000 Incorrect Use of QRI ΓòÉΓòÉΓòÉ Explanation: The Queued Response indicator (QRI) was specified incorrectly; for example, QRI=QR on an expedited-flow request. ΓòÉΓòÉΓòÉ 6.6.8. 40190000 Incorrect Indicators with Last-In-Chain Request ΓòÉΓòÉΓòÉ Explanation: A last-in-chain request has specified incompatible RH settings; for example, RQE, CEBI=╨║CEB, and CDI=╨║CD. ΓòÉΓòÉΓòÉ 6.7. X'80' Path Error ΓòÉΓòÉΓòÉ This category indicates that the request could not be delivered to the intended receiver because of a path outage, an invalid sequence of activation requests, or one of the listed path information unit (PIU) errors. Some PIU errors fall into other categories; for example, sequence number errors are sense code category X'20'. A path error received while the session is active generally indicates that the path to the session partner no longer exists. Select a sense code for specific information. 80020000 Link Failure 8003xxxx NAU Inoperative 8004xxxx Unrecognized Destination 80050000 No Session 80060000 Invalid Format Identifier (FID) Field 8007xxxx Segmenting Error 80080000 PU Not Active 800Fxxxx Invalid Address Combination 8014xxxx No Path Exists to the Destination Node 8020xxxx Session Reset ΓòÉΓòÉΓòÉ 6.7.1. 80020000 Link Failure ΓòÉΓòÉΓòÉ Explanation: Data link failure. It is possible that Communications Manager is not active on the partner machine. ΓòÉΓòÉΓòÉ 6.7.2. 8003xxxx NAU Inoperative ΓòÉΓòÉΓòÉ Explanation: The network accessible unit (NAU) is unable to process requests or responses; for example, the NAU has been disrupted by an abnormal termination. The possible values for bytes 2 and 3 are: 0001 0003 0004 ΓòÉΓòÉΓòÉ 6.7.2.1. 80030001 ΓòÉΓòÉΓòÉ Hierarchical reset. The identified LU-LU session is being deactivated; an ACTLU/ACTPU(Cold) or DACTLU/DACTPU was received, or the PU has failed. ΓòÉΓòÉΓòÉ 6.7.2.2. 80030003 ΓòÉΓòÉΓòÉ Unrecoverable LU failure. The identified LU-LU session had to be deactivated because of an abnormal termination of the PLU or SLU; recovery from the failure was not possible. ΓòÉΓòÉΓòÉ 6.7.2.3. 80030004 ΓòÉΓòÉΓòÉ Recoverable LU failure. The identified LU-LU session had to be deactivated because of an abnormal termination of one of the LUs of the session; recovery from the failure may be possible. ΓòÉΓòÉΓòÉ 6.7.3. 8004xxxx Unrecognized Destination ΓòÉΓòÉΓòÉ Explanation: A node in the path has no routing information for the destination specified either by the SLU name in a BIND request or by the TH. The possible values for bytes 2 and 3 are: 0000 0001 ΓòÉΓòÉΓòÉ 6.7.3.1. 80040000 ΓòÉΓòÉΓòÉ The partner LU name was not recognized. One example of where this could be seen is if your program issues an [MC_]ALLOCATE specifying a fully_qualified_partner_lu_name, but includes the partner LU name only without the network name. ΓòÉΓòÉΓòÉ 6.7.3.2. 80040001 ΓòÉΓòÉΓòÉ A request was received by a gateway function that could not be rerouted because of invalid or incomplete routing information. ΓòÉΓòÉΓòÉ 6.7.4. 80050000 No Session ΓòÉΓòÉΓòÉ Explanation: No half-session is active in the receiving APPN end node for the indicated origination-destination pair, or no boundary function session connector is active for the origin-destination pair in a node providing the boundary function. A session activation request is needed. Possible reasons for this error are: o An ACTLU was received for an LU that APPC does not recognize. When a PU on the host is activated, it typically sends ACTLUs for all LUs it has defined under a PU. APPC negatively responds with this sense code to the ACTLUs for unrecognized LUs. Each negative response is logged in the error log. Generally, you can ignore these entries in the error log. This error log may occur frequently when connecting to a host for 3270 emulation. o A partner LU was sending large chunks of data (probably from a [MC_]SEND_DATA verb with a large data size), and the local LU issued an UNBIND(CLEANUP). The incoming data is rejected with this error log. The following is an example of the error log data, which consists of a TH, RH, and RU: 2E0001020000830100 Where: TH: 2E0001020000 RH: 830100 RU: none ΓòÉΓòÉΓòÉ 6.7.5. 80060000 Invalid Format Identifier (FID) Field ΓòÉΓòÉΓòÉ Explanation: The FID is the first half-byte of any transmission header (TH). For example, if the TH is off by a byte, so the first byte would be X'00'. APPC only supports FID 2 in LU 6.2. ΓòÉΓòÉΓòÉ 6.7.6. 8007xxxx Segmenting Error ΓòÉΓòÉΓòÉ Explanation: The first BIU segment had less than 10 bytes, or a Mapping field sequencing error (such as first, last, middle) occurred, or segmenting was not supported and the Mapping field was not set to BBIU, EBIU. Other allowed settings for bytes 2 and 3 are: 0000 0001 0002 ΓòÉΓòÉΓòÉ 6.7.6.1. 80070000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.7.6.2. 80070001 ΓòÉΓòÉΓòÉ The node does not support receipt of segments, and a Mapping field value other than BBIU, EBIU was received. Sent in UNBIND. ΓòÉΓòÉΓòÉ 6.7.6.3. 80070002 ΓòÉΓòÉΓòÉ Interleaved BIND segments not allowed. A BIND receiver that is in the middle of receiving segments of one BIND receives a segment from a different BIND; the receiver rejects both BINDs and disconnects the link. ΓòÉΓòÉΓòÉ 6.7.7. 80080000 PU Not Active ΓòÉΓòÉΓòÉ Explanation: The SSCP-PU secondary half-session in the receiving node has not been activated and the request was not ACTPU for this half-session. For example, the request was ACTLU from an SSCP that does not have an active SSCP-PU session with the PU associated with the addressed LU. ΓòÉΓòÉΓòÉ 6.7.8. 800Fxxxx Invalid Address Combination ΓòÉΓòÉΓòÉ Explanation: The address combination is invalid. The possible values for bytes 2 and 3 are: 0000 0001 ΓòÉΓòÉΓòÉ 6.7.8.1. 800F0000 ΓòÉΓòÉΓòÉ The (DAF', OAF') (FID2) combination or the LSID (FID3) specified an invalid type of session, for example, a PU-LU combination. ΓòÉΓòÉΓòÉ 6.7.8.2. 800F0001 ΓòÉΓòÉΓòÉ The FID2 ODAI setting in a received BIND is incorrect; the BIND is rejected. ΓòÉΓòÉΓòÉ 6.7.9. 8014xxxx No Path Exists to the Destination Node ΓòÉΓòÉΓòÉ Explanation: Route Selection services in the control point (CP) has determined from the topology database that no path exists to the destination node. The possible values for bytes 2 and 3 are: 0001 0003 0005 ΓòÉΓòÉΓòÉ 6.7.9.1. 80140001 ΓòÉΓòÉΓòÉ No route to the destination node exists for the specified class of service. ΓòÉΓòÉΓòÉ 6.7.9.2. 80140003 ΓòÉΓòÉΓòÉ The topology database indicates that the destination node is not available now; the node either has inconsistent data or is quiescing. ΓòÉΓòÉΓòÉ 6.7.9.3. 80140005 ΓòÉΓòÉΓòÉ The Route Selection control vector (RSCV) specifying the route to the destination node was truncated. ΓòÉΓòÉΓòÉ 6.7.10. 8020xxxx Session Reset ΓòÉΓòÉΓòÉ Explanation: The LU-LU session identified in the UNBIND is being deactivated because of a reset condition. The possible values for bytes 2 and 3 are: 0000 0001 0003 0004 0007 ΓòÉΓòÉΓòÉ 6.7.10.1. 80200000 ΓòÉΓòÉΓòÉ No specific code applies. ΓòÉΓòÉΓòÉ 6.7.10.2. 80200001 ΓòÉΓòÉΓòÉ Virtual route inoperative. The virtual route used by the LU-LU session has become inoperative, thus forcing the deactivation of the identified LU-LU session. ΓòÉΓòÉΓòÉ 6.7.10.3. 80200003 ΓòÉΓòÉΓòÉ Virtual route deactivated. The identified LU-LU session had to be deactivated because of a forced deactivation of the virtual route being used by the LU-LU session. ΓòÉΓòÉΓòÉ 6.7.10.4. 80200004 ΓòÉΓòÉΓòÉ Route extension failure. The route extension used by the LU-LU session has become inoperative, thus forcing the deactivation of the identified LU-LU session. ΓòÉΓòÉΓòÉ 6.7.10.5. 80200007 ΓòÉΓòÉΓòÉ Third-party termination. The network operator cause the forced or cleanup termination of the LU-LU session. ΓòÉΓòÉΓòÉ 6.8. X'FF' Product Unique Errors ΓòÉΓòÉΓòÉ This category indicates a condition was detected by the node that is not defined in SNA. The sense code defined is unique to this implementation. Select a sense code for specific information. FFFExxxx FFFFxxxx Directory Function Error ΓòÉΓòÉΓòÉ 6.8.1. FFFExxxx ΓòÉΓòÉΓòÉ Explanation: The possible values for bytes 2 and 3 are: 0011 0012 0013 0014 0015 0016 0017 0018 0019 001A 0101 0102 0103 0104 0105 0106 0107 0108 0109 010A 010B 010C 010D 010E 010F 0110 0111 0112 0113 0114 0115 xx3x ΓòÉΓòÉΓòÉ 6.8.1.1. FFFE0011 ΓòÉΓòÉΓòÉ CNOS negotiation in progress. An [MC_]ALLOCATE or [MC_]SEND_CONVERSATION was attempted while CNOS contention winner negotiation is occurring in another OS/2 process or thread, from the same local LU to the same partner LU. Session limits are currently being negotiated with your partner, because of a previous allocation attempt or a CNOS verb. This condition continues until the previous session limit negotiation is completed. Operator Response: Retry the operation. This condition is timing related. ΓòÉΓòÉΓòÉ 6.8.1.2. FFFE0012 ΓòÉΓòÉΓòÉ APPC not started. An [MC_]ALLOCATE or [MC_]SEND_CONVERSATION attempted while APPC has not been started by Communications Manager. Operator Response: Retry the operation. This condition is timing related. ΓòÉΓòÉΓòÉ 6.8.1.3. FFFE0013 ΓòÉΓòÉΓòÉ A mode, other than CPSVCMG or SNASVCMG, is pending a delete. Unable to issue an [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb for this mode while the mode is in pending delete state. Pending delete state is attained by issuing DEFINE_MODE with changes, or DELETE_MODE. These verbs do not go into effect until all sessions using this mode are inactive. ΓòÉΓòÉΓòÉ 6.8.1.4. FFFE0014 ΓòÉΓòÉΓòÉ The CPSVCMG mode is pending a delete. APPC is unable to internally issue an ALLOCATE verb for this mode while the mode is in pending delete state. ΓòÉΓòÉΓòÉ 6.8.1.5. FFFE0015 ΓòÉΓòÉΓòÉ The SNASVCMG mode is pending a delete. APPC is unable to internally issue an ALLOCATE verb for this mode while the mode is in pending delete state. Pending delete state is attained by issuing DEFINE_MODE with changes, or DELETE_MODE. These verbs do not take effect until all sessions using this mode are inactive. ΓòÉΓòÉΓòÉ 6.8.1.6. FFFE0016 ΓòÉΓòÉΓòÉ Session unavailable on a mode other than CPSVCMG or SNASVCMG. An [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb with type(WHEN_SESSION_FREE) was attempted, but no pending or bindable sessions are available. ΓòÉΓòÉΓòÉ 6.8.1.7. FFFE0017 ΓòÉΓòÉΓòÉ Session unavailable on a CPSVCMG mode. APPC issued an internal ALLOCATE verb with type(WHEN_SESSION_FREE) attempted, but no pending or bindable sessions are available. ΓòÉΓòÉΓòÉ 6.8.1.8. FFFE0018 ΓòÉΓòÉΓòÉ Session unavailable on an SNASVCMG mode. APPC issued an internal ALLOCATE verb with type(WHEN_SESSION_FREE) attempted, but no pending or bindable sessions are available. ΓòÉΓòÉΓòÉ 6.8.1.9. FFFE0019 ΓòÉΓòÉΓòÉ Partner CNOS race condition. APPC issued an internal CNOS verb. Although its primary return was PARTNER_REJECT and the secondary return code was CNOS_RACE, no sense code associated with the returned verb was generated. Operator Response: Retry the operation. This condition is timing related. ΓòÉΓòÉΓòÉ 6.8.1.10. FFFE001A ΓòÉΓòÉΓòÉ This code is returned when a second ACTLU or a DACTPU is received on a session that is pending activation. This occurs only during subarea session activation. ΓòÉΓòÉΓòÉ 6.8.1.11. FFFE0101 ΓòÉΓòÉΓòÉ Last session deactivated on a mode other than CPSVCMG or SNASVCMG. This code is returned on [MC_]ALLOCATE or [MC_]SEND_CONVERSATION when return_control is WHEN_SESSION_ALLOCATED, or WHEN_SESSION_FREE. A queued session request is rejected because the last session on the requested mode was deactivated. Therefore, the [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb is not fulfilled and is returned with this sense data. ΓòÉΓòÉΓòÉ 6.8.1.12. FFFE0102 ΓòÉΓòÉΓòÉ Last session deactivated on a CPSVCMG mode. APPC issued an internal ALLOCATE verb with return_control(WHEN_SESSION_ALLOCATED) or return_control(WHEN_SESSION_FREE). A queued session request is rejected because the last session on the requested mode was deactivated. Therefore, the ALLOCATE verb is not fulfilled and is returned with this sense data. ΓòÉΓòÉΓòÉ 6.8.1.13. FFFE0103 ΓòÉΓòÉΓòÉ Last session deactivated on an SNASVCMG mode. APPC issued an internal ALLOCATE verb with return_control(WHEN_SESSION_ALLOCATED) or return_control(WHEN_SESSION_FREE). A queued session request is rejected because the last session on the requested mode was deactivated. Therefore the ALLOCATE verb is not fulfilled and is returned with this sense data. ΓòÉΓòÉΓòÉ 6.8.1.14. FFFE0104 ΓòÉΓòÉΓòÉ Last contention winner session is deactivated on a mode other than CPSVCMG or SNASVCMG. This code is returned on [MC_]ALLOCATE or [MC_]SEND_CONVERSATION when return_control(WHEN_CONWINNER_ALLOCATED). A queued session request is rejected because the last session on the requested mode was deactivated. Therefore, the [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb is not fulfilled and is returned with this sense data. ΓòÉΓòÉΓòÉ 6.8.1.15. FFFE0105 ΓòÉΓòÉΓòÉ Last contention winner session is deactivated on a CPSVCMG mode. An internal ALLOCATE verb with return_control(WHEN_CONWINNER_ALLOCATED) was issued by APPC. A queued session request is rejected because the last session on the requested mode was deactivated. Therefore, the ALLOCATE verb is not fulfilled and is returned with this sense data. ΓòÉΓòÉΓòÉ 6.8.1.16. FFFE0106 ΓòÉΓòÉΓòÉ Last contention winner session is deactivated on an SNASVCMG mode. An internal ALLOCATE verb with return_control(WHEN_CONWINNER_ALLOCATED) was issued by APPC. A queued session request is rejected because the last session on the requested mode was deactivated. Therefore, the ALLOCATE verb is not fulfilled and is returned with this sense data. ΓòÉΓòÉΓòÉ 6.8.1.17. FFFE0107 ΓòÉΓòÉΓòÉ Associated session for a conversation group is deactivated. This code is returned on the [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb when return_control(WHEN_CONV_GROUP_ALLOC). A queued session request is rejected because the last session on the requested mode was deactivated. Therefore, the [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb is not fulfilled and is returned with this sense data. ΓòÉΓòÉΓòÉ 6.8.1.18. FFFE0108 ΓòÉΓòÉΓòÉ Associated session for conversation group is not defined. An [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb was issued, with type(WHEN_CONV_GROUP_ALLOC) specified, and no session is available. A likely cause of this sense data is that your program supplied an invalid conversation_group_id parameter on an [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb. A list of valid conversion group IDs can be found by using subsystem management. ΓòÉΓòÉΓòÉ 6.8.1.19. FFFE0109 ΓòÉΓòÉΓòÉ Contention winner session was never available on a mode other than CPSVCMG or SNASVCMG. [MC_]ALLOCATE or [MC_]SEND_CONVERSATION with type(WHEN_CONWINNER_ALLOCATED) was specified. The mode's minimum contention winner value is 0 and no session is available. ΓòÉΓòÉΓòÉ 6.8.1.20. FFFE010A ΓòÉΓòÉΓòÉ Contention winner session was never available on CPSVCMG mode. An internal ALLOCATE verb with return_control(WHEN_CONWINNER_ALLOCATED) was issued by APPC. The mode's minimum contention winner value is 0 and no session is available. ΓòÉΓòÉΓòÉ 6.8.1.21. FFFE010B ΓòÉΓòÉΓòÉ Contention winner session was never available on SNASVCMG mode. An internal ALLOCATE verb with return_control(WHEN_CONWINNER_ALLOCATED) was issued by APPC. The mode's minimum contention winner value is 0 and no session is available. ΓòÉΓòÉΓòÉ 6.8.1.22. FFFE010C ΓòÉΓòÉΓòÉ Session was never available on a mode other than CPSVCMG or SNASVCMG. This sense data can be caused by one of the following conditions: o An [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb was issued with return_control(WHEN_SESSION_ALLOCATED) or return_control(WHEN_SESSION_FREE). The mode's session limit is 0 and no session is available. o An [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verb was issued with return_control(WHEN_SESSION_ALLOCATED) or return_control(WHEN_SESSION_FREE). The target machine has set the mode session limit for this mode to 0. o The BIND for a subarea session was successful, but APPC changed the number of sessions to 0 before ACTLU arrived. ΓòÉΓòÉΓòÉ 6.8.1.23. FFFE010D ΓòÉΓòÉΓòÉ Session was never available on a CPSVCMG mode. This sense data can be caused by one of the following conditions: o APPC issued an internal ALLOCATE verb with return_control(WHEN_SESSION_ALLOCATED) or return_control(WHEN_SESSION_FREE). The mode's session limit is 0 and no session is available. o APPC issued an internal ALLOCATE verb with return_control(WHEN_SESSION_ALLOCATED) or return_control(WHEN_SESSION_FREE). The target machine has set the mode session limit for this mode to 0. o The BIND for a subarea session was successful, but APPC changed the number of sessions to 0 before ACTLU arrived. ΓòÉΓòÉΓòÉ 6.8.1.24. FFFE010E ΓòÉΓòÉΓòÉ Session was never available on an SNASVCMG mode. This sense data can be caused by one of the following conditions: o An internal ALLOCATE verb with return_control(WHEN_SESSION_ALLOCATED) or return_control(WHEN_SESSION_FREE) was issued by APPC. The mode's session limit is 0 and no session is available. o An internal ALLOCATE verb with return_control(WHEN_SESSION_ALLOCATED) or return_control(WHEN_SESSION_FREE) was issued by APPC. The target machine has set the mode session limit for this mode to 0. o The BIND for a subarea session was successful, but APPC changed the number of sessions to 0 before ACTLU arrived. ΓòÉΓòÉΓòÉ 6.8.1.25. FFFE010F ΓòÉΓòÉΓòÉ The SNASVCMG mode does not exist. If the SNASVCMG mode does not exist, and APPC is executing its internal CNOS transaction program to control parallel sessions, this sense data occurs. Since the SNASVCMG mode should always be defined, this signals an error condition. ΓòÉΓòÉΓòÉ 6.8.1.26. FFFE0110 ΓòÉΓòÉΓòÉ A remote mode, other than CPCVSMG or SNASVCMG, is closed or does not exist. Usually, this means that the mode is not defined correctly at the partner, or the number of sessions was changed to 0. APPC issued an internal CNOS verb, and its primary return was PARTNER_REJECT and the secondary return code was MODE_CLOSED or BAD_MODE. No sense code was associated with the returned verb. ΓòÉΓòÉΓòÉ 6.8.1.27. FFFE0111 ΓòÉΓòÉΓòÉ A remote CPSVCMG mode is closed or does not exist. APPC issued an internal CNOS verb. Its primary return code was PARTNER_REJECT and the secondary return code was MODE_CLOSED or BAD_MODE. No sense code was associated with the returned verb. Usually, this means that the mode is not defined correctly at the partner, or the number of sessions was changed to 0. ΓòÉΓòÉΓòÉ 6.8.1.28. FFFE0112 ΓòÉΓòÉΓòÉ A remote SNASVCMG mode is closed or does not exist. APPC issued an internal CNOS verb, and its primary return code was PARTNER_REJECT and the secondary return code was MODE_CLOSED or BAD_MODE. No sense code was associated with the returned verb. Usually, this means that the mode is not defined correctly at the partner, or the number of sessions was changed to 0. ΓòÉΓòÉΓòÉ 6.8.1.29. FFFE0113 ΓòÉΓòÉΓòÉ Link is defined as a Subarea Only. The network accessible unit (NAU) was configured as nonzero; this link can only be used for dependent LUs. ΓòÉΓòÉΓòÉ 6.8.1.30. FFFE0114 ΓòÉΓòÉΓòÉ Path control ID is mismatched for subarea. Mismatch between the PC IDs in the ACTLU and the INITSELF RUs. ΓòÉΓòÉΓòÉ 6.8.1.31. FFFE0115 ΓòÉΓòÉΓòÉ The CNOS TP on the target node provided an invalid response. This sense code is indicative of an SNA-internal error. ΓòÉΓòÉΓòÉ 6.8.1.32. FFFExx3x ΓòÉΓòÉΓòÉ An ISDN connection manager error has occurred. If the third byte is 30 or 33, then the next to the last byte is the ISDN completion code. Refer to ISDN Port Connection Manager (PCM) Programming Reference for additional information. If the third byte is 34, then the next to the last byte is the CCITT cause value. Refer to International Telegraph and Telephone Consutative Committee (CCITT), Recommendation Q.931 for additional information. ΓòÉΓòÉΓòÉ 6.8.2. FFFFxxxx Directory Function Error ΓòÉΓòÉΓòÉ Explanation: An error occurred while performing a directory search or directory delete. The possible values for bytes 2 and 3 are: 0002 0003 0006 0007 F004 ΓòÉΓòÉΓòÉ 6.8.2.1. FFFF0002 ΓòÉΓòÉΓòÉ Multiple resources found. Resource must be unique. A network search for a resource required to have a unique name has returned multiple positive replies from different owners. Only one resource should have that name. The other resources should be renamed or deleted, otherwise the first resource found in the search is returned. ΓòÉΓòÉΓòÉ 6.8.2.2. FFFF0003 ΓòÉΓòÉΓòÉ No link. No NNCP server was found when trying to issue an [MC_]ALLOCATE verb and find the associated partner LU. This sense code indicates that a session activation failed because APPC could not find a link to connect it to the partner node. If your node is serviced by an APPN network node, this sense code means that your node could not contact that network node (probably because the link is down or defined incorrectly). If your node is not serviced by an APPN network node, it means that you have not provided a valid DEFINE_PARTNER_LU_LOCATION verb together with a DEFINE_LOGICAL_LINK verb, which specifies the link to use. Be sure the DEFINE_LOGICAL_LINK verb contains a valid fq_adjacent_cp_name parameter and the link is either active, or defined as activate_at_startup(NO) (which brings it up immediately, as opposed to when Communications Manager is started). One of the following can cause a directory function error to occur: o Your node does not have a link to an APPN network node; thus it has no place to send the locate RU. o Your node does not have a link to the target node, where the searched-for LU is located. Examples of how this can happen: o There is a bad target MAC address for the APPN network node. o The data link control (DLC) was deactivated on either machine. o Communications Manager is not fully started yet on your local workstation, and the links have not yet been activated. There are no message log or error log entries associated with this sense data. ΓòÉΓòÉΓòÉ 6.8.2.3. FFFF0006 ΓòÉΓòÉΓòÉ Cannot delete a local node directory entry. An APPN end node sent a Delete generalized data stream (GDS) variable, requesting that the CP LU be deleted. This cannot be performed. ΓòÉΓòÉΓòÉ 6.8.2.4. FFFF0007 ΓòÉΓòÉΓòÉ Address space unknown. The node has received data or is trying to send data on a link station that is not in its local address space. The node has canceled processing of the data. ΓòÉΓòÉΓòÉ 6.8.2.5. FFFFF004 ΓòÉΓòÉΓòÉ APPN unloading. The APPN control point is informing a locally registered MS application that the control point is being unloaded. When APPN restarts, the application will not be registered. It must reregister using the REGISTER_MS_APPLICATION verb to receive incoming MDS-MUs. ΓòÉΓòÉΓòÉ 7. OS/2 Request Codes ΓòÉΓòÉΓòÉ Error log entries with major error code 22 contain information about the OS/2 API which failed. You can find information about the failed function in one or both of the following areas (depending on the failure): o The Extra Symptom Data may contain the name of the failed function (identified by API/). o The minor error code identifies the OS/2 request code associated with a function. Once you have identified the OS/2 request code, you can use the table in the associated window to translate between request codes and OS/2 function calls. ΓòÉΓòÉΓòÉ 7.1. Request Codes and Function Calls ΓòÉΓòÉΓòÉ Request Associated Function Call Code ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1001 DosICreateThread ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1002 DosCWait ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1003 DosEnterCritSec ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1004 DosIExecPgm ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1005 DosExit ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1006 DosExitCritSec ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1007 DosExitList ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1008 DosGetInfoSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1009 DosGetPrty ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 100A DosKillProcess ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 100B DosSetPrty ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 100C DosPTrace ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 100D DosHoldSignal ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 100E DosSetSigHandler ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 100F DosFlagProcess ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1010 DosMakePipe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1011 DosISysSemClear ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1012 DosISemRequest ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1013 DosISemSetWait ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1014 DosSemSetWait ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1015 DosISemWait ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1016 DosMuxSemWait ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1017 DosCloseSem ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1018 DosCreateSem ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1019 DosOpenSem ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 101A DosResumeThread ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 101B DosSuspendThread ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 101C DosSetDateTime ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 101D DosTimerAsync ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 101E DosTimerStart ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 101F DosTimerStop ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1020 DosSleep ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1021 DosGetDateTime ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1022 DosAllocSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1023 DosAllocShrSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1024 DosGetShrSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1025 DosGiveSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1026 DosReallocSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1027 DosFreeSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1028 DosAllocHuge ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1029 DosGetHugeShift ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 102A DosReallocHuge ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 102B DosCreateCSAllias ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 102C DosLoadModule ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 102D DosGetProcAddr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 102E DosFreeModule ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 102F DosGetModHandle ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1030 DosGetModName ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1031 DosGetResource ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1032 DosGetMachineMode ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1033 DosBeep ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1034 DosCLIAccess ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1035 DosDevConfig ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1036 DosDevIOCtl ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1037 DosSgSwitch ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1038 DosSgSwitchMe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1039 DosBufReset ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 103A DosChDir ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 103B DosChgFilePtr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 103C DosClose ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 103D DosDelete ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 103E DosDupHandle ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 103F DosFileLocks ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1040 DosFindClose ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1041 DosFindFirst ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1042 DosFindNext ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1043 DosMkDir ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1044 DosMove ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1045 DosNewSize ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1046 DosPortAccess ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1047 DosOpen ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1048 DosQCurDir ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1049 DosQCurDisk ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 104A DosQFHandState ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 104B DosQFileInfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 104C DosQFileMode ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 104D DosQFsInfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 104E DosQHandType ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 104F DosQVerify ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1050 DosIRead ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1051 DosRmDir ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1052 DosSelectDisk ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1053 DosSetFHandState ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1054 DosSetFileInfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1055 DosSetFileMode ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1056 DosSetMaxFH ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1057 DosSetVerify ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1058 DosIWrite ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1059 DosSystemService ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 105A DosSetVec ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 105B DosSysTrace ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 105C DosGetEnv ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 105D DosGetVersion ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 105E DosQTraceInfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 105F DosGetPID ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1060 DosSicG ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1061 DosLibInit ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1062 DosSetFsInfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1063 DosDataPath ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1064 DosJoin ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1065 DosSubSt ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1066 DosQSwitchAr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1067 DosICanonicalize ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1068 DosSetFgnd ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1069 DosSwapTaskInit ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 106A DosReadPhys ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 106B DosPokeTestDaemon ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 106C DosPanicWrite ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 106D DosStruCheck ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 106E DosStruResUpdate ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 106F DosGetHeaders ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1070 DosDbGetKVar ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1071 DosGetSelAddr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1072 DosGetAddr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1073 DosDBMemLock ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1074 DosDBMemUnlock ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1075 DosDBSegAlloc ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1076 DosDBMemRealloc ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1077 DosDBMemFree ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1078 DosDBGetOwner ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1079 DosDBPhysInfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 107A DosGetStdA ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 107B DosError ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 107C DosGetSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 107D DosLockSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 107E DosUnlockSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 107F DosSgSwitchProc ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1080 DosIRamSemWake ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1081 DosIQCtryCode ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1082 DosSizeSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1083 DosMemAvail ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1084 DosSetInfoSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1085 DosPhysicalDisk ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1086 DosGetCP ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1087 DosSetCP ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1088 DosGlobalSeg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1089 DosDBProfile ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 108A DosHugeShift ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 108B DosHugeIncr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 108C DosSendSignal ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 108D DosOpen2 ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 108F DosEnumAttribute ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1090 DosCallback ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1091 DosCopy ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1092 DosDevIOCtl2 ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1093 DosEditName ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1094 DosFileIO ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1095 DosFindFirst2 ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1096 DosFreeResource ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1097 DosFSAttach ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1098 DosFSCtl ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 1099 DosGetPPID ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 109A DosGetResource2 ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 109B DosMkDir2 ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 109C DosQAppType ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 109D DosQFSAttach ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 109E DosQPathinfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 109F DosQSysinfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 10A0 DosR2StackRealloc ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 10A1 DosSetPathinfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 10A2 DosSetProccp ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 10A3 DosShutdown ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2001 KbdRegister ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2002 KbdDeRegister ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2003 KbdCharIn ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2004 KbdFlushBuffer ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2005 KbdGetStatus ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2006 KbdPeek ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2007 KbdSetStatus ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2008 KbdStringIn ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2009 KbdOpen ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 200A KbdClose ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 200B KbdGetFocus ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 200C KbdFreeFocus ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 200D KbdGetCP ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 200E KbdSetCP ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 200F KbdXLate ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2010 KbdSetCustXt ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2011 KdbGetHWId ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2012 KdbSetFgnd ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 2013 KbdSynch ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 3001 DosMonOpen ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 3002 DosMonClose ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 3003 DosMonReg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 3004 DosMonRead ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 3005 DosMonWrite ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4001 MouRegister ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4002 MouDeRegister ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4003 MouFlushQue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4004 MouGetHotKey ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4005 MouSetHotKey ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4006 MouGetPtrPos ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4007 MouSetPtrPos ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4008 MouGetPtrShape ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4009 MouSetPtrShape ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 400A MouGetDevStatus ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 400B MouGetNumButtons ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 400C MouGetNumMickeys ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 400D MouReadEventQue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 400E MouGetNumQueEl ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 400F MouGetEventMask ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4010 MouSetEventMask ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4011 MouGetScaleFact ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4012 MouSetScaleFact ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4013 MouOpen ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4014 MouClose ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4015 MouRemovePtr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4016 MouDrawPtr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4017 MouSetDevStatus ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4018 MouInitReal ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 4019 MouSynch ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 5001 DosTrueGetMessage ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 5002 DosInsMessage ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 5003 DosPutMessage ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 5004 DosGetMessage ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6001 DosGetCtryInfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6002 DosGetDBCSEv ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6003 DosCaseMap ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 6004 DosGetCollate ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 7001 DosCloseQueue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 7002 DosCreateQueue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 7003 DosOpenQueue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 7004 DosPeekQueue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 7005 DosPurgeQueue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 7006 DosQueryQueue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 7007 DosReadQueue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 7008 DosWriteQueue ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8001 VioRegister ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8002 VioDeRegister ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8003 VioGetBuf ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8004 VioGetCurPos ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8005 VioGetCurType ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8006 VioGetMode ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8007 VioGetPhysBuf ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8008 VioReadCellStr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8009 VioReadCharStr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 800A VioScrollDn ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 800B VioScrollUp ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 800C VioScrollLf ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 800D VioScrollRt ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 800E VioSetCurPos ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 800F VioSetCurType ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8010 VioSetMode ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8011 VioShowBuf ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8012 VioWrtCellStr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8013 VioWrtCharStr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8014 VioWrtCharStrAtt ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8015 VioWrtNAttr ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8016 VioWrtNCell ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8017 VioWrtNChar ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8018 VioWrtTTY ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8019 VioSetAnsi ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 801A VioGetAnsi ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 801B VioPrtSc ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 801C VioPrtScToggle ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 801D VioSavRedrawWait ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 801E VioSavRedrawUndo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 801F VioModeWait ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8020 VioModeUndo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8021 VioScrLock ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8022 VioScrUnLock ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8023 VioPopUp ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8024 VioEndPopUp ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8025 VioGetConfig ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8026 VioGetFont ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8027 VioGetCP ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8028 VioSetCP ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8029 VioSetFont ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 802A VioGetState ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 802B VioSetState ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 802C VioAssociate ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 802D VioCreateLogFont ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 802E VioCreatePS ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 802F VioDeleteSetID ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8030 VioDestroyPS ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8031 VioGetOrg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8032 VioQueryFonts ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8033 VioQuerySetIDs ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8034 VioSetDeviceCellSize ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8035 VioSetOrg ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8036 VioShowPS ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 8037 VioGetDeviceCellSize ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9001 DosRead ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9002 DosWrite ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9003 DosErrClass ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9004 DosSemRequest ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9005 DosSemClear ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9006 DosSemWait ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9007 DosSemSet ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9008 DosExecPgm ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9009 DosCreateThread ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 900A DosSubSet ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 900B DosSubAlloc ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 900C DosSubFree ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 900D DosReadAsync ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 900E DosWriteAsync ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 900F DosSearchPath ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9010 DosScanEnv ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9011 DosFSRAMSemRequest ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9012 DosFSRAMSemClear ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9101 DosCallNmPipe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9102 DosConnectNmPipe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9103 DosDisconnectNmPipe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9104 DosMakeNmPipe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9105 DosPeekNmPipe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9106 DosQNmHandState ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9107 DosQNmPipeInfo ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9108 DosQNmPipeSemState ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 9109 DosSetNmPHandState ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 910A DosSetNmPipeSem ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 910B DosTransactNmPipe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ 910C DosWaitNmPipe ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ A001 DosStartSession. If the originator is APPC, this error may have occurred because APPC attempted to start a TP (through the attach manager), but there was not enough memory. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ A002 DosSetSession ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ A003 DosSelectSession ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ A004 DosStopSession. ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ A005 DosSMRegisterDD ΓòÉΓòÉΓòÉ 8. Contacting IBM ΓòÉΓòÉΓòÉ IBM provides assistance for suspected program defects. This chapter contains procedures for contacting IBM. Select one of the following categories: o When to Contact IBM o Sending Problem Determination Information to IBM (for U.S.A. Users) ΓòÉΓòÉΓòÉ 8.1. When to Contact IBM ΓòÉΓòÉΓòÉ The services IBM provides are designed as part of an overall problem determination process. Use the procedures and facilities described in this appendix and on your Service and Support Information Card only after you have: o Followed a problem path in Problem Determination Procedures that instructs you to contact IBM. OR o Responded to a message as directed and were instructed to contact IBM Utilize your local support personnel before contacting IBM. Only persons with in-depth knowledge of the problem should contact IBM; therefore, support personnel should act as the interface with IBM. If you determine that you need to contact IBM, refer to your Service and Support Information Card for a detailed description of the services IBM provides. This card also contains information on how to contact IBM. ΓòÉΓòÉΓòÉ 8.2. Sending Problem Determination Information to IBM (for U.S.A. ΓòÉΓòÉΓòÉ Users) Information should be sent to IBM for analysis only upon direction from the IBM Support Center. If, upon contacting IBM using the procedures provided earlier in this chapter, an IBM Support Center representative requests that you send information to IBM, read the information in this chapter before sending the information. The information in this section describes: o Your right to privacy o Mailing labels you should attach to packages mailed to IBM ΓòÉΓòÉΓòÉ 8.2.1. Understanding Your Right to Privacy ΓòÉΓòÉΓòÉ Do not send IBM information that is considered to be confidential or proprietary by you or the end user. IBM is under no obligation of any kind with regard to information or material submitted by customers. IBM reserves the right to publish or disclose such information to third parties. Send only copies of problem report information to IBM. Keep originals for your own records. IBM does not return printouts, diskettes, or other problem determination data received from customers. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ These are windows that "pop up" on the screen to let you know when an error occurs. Many pop-up messages allow you to select Help to view help for the message. The file \CMLIB\ALRTNPOP.TXT allows you to override the pop-up capability of up to 200 ACS messages. You can specify message numbers for messages that you do not want to pop up on your screen; however, messages that are intended to be logged are still logged. By default, this file suppresses the pop-up capability of several messages associated with certain alerts. Note: All alert messages are logged. Some messages are popped up but not logged. If you suppress pop-up capability for a message that is not logged, you may not have any notification or record that an event occurred. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ This is the message logging facility. Use this facility to access Communications Manager messages in the default FFST/2 message log (OS2MLOG.DAT) and in other message logs defined by Communications Manager. When you receive a message, the first thing you should do is view the message in the message log formatter. Read the entire message and the message help and perform the actions indicated. If the message instructs you to look in the system error log or the FFST/2 dump formatter, note the time of the message and the problem ID to help you access the appropriate entries in the system error log and the dump formatter. See Accessing and Using the FFST/2 Message Log for more information. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ The system error log is an OS/2 facility that contains information about the error and the environment in which the error occurred. The message log formatter often contains messages that describe how to extract information from the system error log. Be sure to check the message log formatter before checking the system error log. See Accessing and Using the System Error Log for more information. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ This is a customized dump facility that can contain detailed information about the error and the environment in which the error occurred. Communications Manager uses this facility to supply and format detailed information about alerts. Note: FFST/2 supports an SNA generic alert and alert routing service that can route alerts to the host for attention. See Accessing and Using the FFST/2 Dump Formatter for more information. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ The message console is a window you can activate to view messages as they are logged. This service provides a similar function to the message log formatter; however, when you close the message console, its contents are erased. For Communications Manager, use the message log formatter the focal point for problem determination and use the message console for configuring FFST/2. See Accessing and Using the FFST/2 Message Console for more information. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ You can use the command line interface instead of or in addition to the windowed interface. See Using the FFST/2 Command Line Interface for more information. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ When you select ON, all of the FFST/2 runtime capabilities are activated. When you select OFF, all of the FFST/2 runtime capabilities are deactivated. All of the windowed interfaces are still available. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ When you select ON, FFST/2 displays pop-up messages. When you select OFF, FFST/2 suppresses pop-up messages; however, all other FFST/2 services continue to function normally. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ Under System, you can specify the maximum number of system software customized dump files that may occur in the current system dump directory. You can also configure the default dump path name for logging of system software customized dumps. System software customized dump files are named OS2SYSxx.DMP, where xx can range from 01 to maximum dumps. If you create enough dumps to exceed the maximum number of dumps, FFST/2 rolls the current dump number over to 01 and overwrites the first dump. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ Under Application, you can specify the maximum number of application software customized dump files that may occur in the current application dump directory. You can also configure the default dump path name for logging of application software customized dumps. Application software customized dump files are named OS2APLxx.DMP, where xx can range from 01 to maximum dumps. If you create enough dumps to exceed the maximum number of dumps, FFST/2 rolls the current dump number over to 01 and overwrites the first dump. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ FFST/2 allows for a single default message log. This log is named OS2MLOG.DAT and is located in the \OS2\SYSTEM directory by default. You can change the path and file name of the default message log. Applications can define their own message logs and these are not configurable. Communications Manager defines the following message logs which are located in the \CMLIB directory: UPGRADE.LOG Contains all messages produced when you upgrade from a prior level of Communications Manager. VERIFY.LOG Contains all messages produced when you verify a configuration. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ OK Implements the initialization and configuration requests and exits the FFST/2 Initialization and Configuration window. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ Cancels the initialization and configuration requests and exits the FFST/2 Initialization and Configuration window. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ Resets all initialization and configuration values to initial defaults. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ The Problem Determination Aids - Trace Services window can be accessed by selecting Problem Determination Aids - Trace Services from the Communications Manager/2 folder. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ Refer to the online Command Reference for information on the CMTRACE command. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ Refer to Application Programming Guide for information on DEFINE_TRACE and other service verbs. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ APPC Programming Guide and Reference, SC31-6160 (20G1556) ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ Refer to the online Command Reference for information on the FMTTRACE command.