APAR status
Closed as canceled.
Error description
+--------------------------------------------------------------+ | Error description abstract: | | | | INFO API debugging techniques | | Last updated: 12/01/94 MTG | +--------------------------------------------------------------+ | Detailed description of APAR: | | | | This informational APAR will provide INFO API users with | | problem debugging techniques. | | | +--------------------------------------------------------------+ | Publication references: | | | | SC34-4463-00 Application Program Interface Guide and | | Reference Version 6 Release 1 for MVS/ESA | | | | | | SC34-4335-00 Application Program Interface Guide and | | Reference Version 5 Release 1 for MVS/ESA | | | | SC34-4187-01 The Information/Family Application Program | | Interfaces Version 4, Release 2, Modification 2 | | | +--------------------------------------------------------------+ | Technical information: | | | | If you are working with the Low level API, LLAPI, make sure | | that you have allocated the APIPRINT data set as follows: | | | | 1. Set the PICAMSGD field to B or P. | | | | 2. Allocate APIMSG_OPTION to SYSOUT or create a sequential | | non-VSAM data set with DCB: | | | | DSORG = PS | | | | RECFM = VBA | | | | LRECL = 125 | | | | BLKSIZE = 6144 | | | | If you are working with the high level API, HLAPI, make sure | | that you have allocated the APIPRINT data set as follows: | | | | 1. Set APIMSG_OPTION to P, C, or B. | | | | 2. Allocate APIMSG_OPTION to SYSOUT or create a sequential | | non-VSAM data set with DCB: | | | | DSORG = PS | | | | RECFM = VBA | | | | LRECL = 125 | | | | BLKSIZE = 6144 | | | | and that you have allocated the HLAPILOG data set as | | follows: | | | | 1. Set HLIMSG_OPTION to P, C, or B. | | | | 2. Allocate APIMSG_OPTION to SYSOUT or create a sequential | | non-VSAM data set with DCB: | | | | DSORG = PS | | | | RECFM = VBA | | | | LRECL = 125 | | | | BLKSIZE = 6144 | | | | If you are working with the REXX/API, make sure that you | | have allocated the APIPRINT data set as follows: | | | | 1. Set the PICAMSGD field to B or P. | | | | 2. Allocate APIMSG_OPTION to SYSOUT or create a sequential | | non-VSAM data set with DCB: | | | | DSORG = PS | | | | RECFM = VBA | | | | LRECL = 125 | | | | BLKSIZE = 6144 | | | | and that you have allocated the HLAPILOG data set as | | follows: | | | | 1. Set HLIMSG_OPTION to P, C, or B. | | | | 2. Allocate APIMSG_OPTION to SYSOUT or create a sequential | | non-VSAM data set with DCB: | | | | DSORG = PS | | | | RECFM = VBA | | | | LRECL = 125 | | | | BLKSIZE = 6144 | | | | 3. Also, specify: | | | | INIT.?PROC='T' | | | | before the INIT (initialize) transaction. | | | | - | | | | The information provided in these output datasets will show | | what API transactions were processed in order and what the | | return and reason code associated with each transaction is | | along with other INFO messages. | | | | | | | | | | Looking Up API Return and Reason Codes: | | | | There has been some confusion over how to look up API return | | and reason codes. Specifically, since the HLAPI uses the | | LLAPI, you may receive either a LLAPI or a HLAPI return and | | reason code when using the HLAPI. One way to determine for | | sure whether or not the return and reason code is associated | | with the LLAPI or the HLAPI is to look for the failing | | transaction in the APIPRINT output and HLAPILOG output. If | | the return and reason code is associated with an APIPRINT | | transaction (transactions for LLAPI start with a T), then | | the return and reason code is for the LLAPI. If the return | | and reason code is associated with a HLAPILOG transaction | | (transactions for HLAPI start with a H), then the return and | | reason code is for the HLAPI. | | | | - | | | | Also, the reason codes for the return codes are unique. For | | example, both the LLAPI and the HLAPI have return code 12 | | (RC12). But, only the LLAPI has reason code 80, and only | | the HLAPI has reason code 47. So, if you look under both | | the LLAPI and the HLAPI return codes for the reason code, | | you should only find it associated with the LLAPI or the | | HLAPI. | | | | | | | | | | Common API errors: | | | | RC12 RC3 is a very common API error. One reason it is | | issued is that one of the API TSPs chose a selection (using | | ADDDATA) that was not on the current panel. Another reason | | is that a TSP is processed at file time for a create or an | | update. When the TSP does a PROCESS, the record filed | | successfully message is lost, and the API does a check for | | the message to insure record creation or update. | | | | - | | | | The best way to gather additional information about what is | | causing the RC12 RC3 is to put a TRACE function line at the | | beginning of the API mainline TSP BLGAPI00 and specify | | 'Trace LINK function' as YES. You will need to allocate | | BLGTRACE to SYSOUT or a dataset. In the TRACE output, look | | for a TSCAFRET or TSCAFRES that is not 0 and follow normal | | TSP function line debugging techniques. You might want to | | add a PRINT function line to the TSP with the error after | | the function line with the nonzero TSCAFRET and/or TSCAFRES. | | The PRINT will show you what panel the error occurred on and | | any messages that were issued. | | | +--------------------------------------------------------------+ | Customer: If you have suggestions to improve this | | informational APAR, please submit a problem record to INFO | | Level 2 Software Support using the appropriate component ID | | listed below. | | | | We appreciate your suggestions. | +--------------------------------------------------------------+ | Following is a list of keywords that you can use to search | | in the RETAIN system: | | INFOINFO RALINFO INFOMAN INFOSYS INFO/MAN INFO/SYS | | INFORMATION SYSTEMS MANAGEMENT MVS V42 V41 V4 V422 V5 | | V51 V6 V61 LVLS/101 LVLS/A02 LVLS/102 LVLS/202 LVLS/222 | | LVLS/290 LVLS/C10 | +--------------------------------------------------------------+ | Following are the components that apply to this APAR: | | COMPID REL FMID FESN PRODUCT DESCRIPTION | +--------------------------------------------------------------+ | 566432301 RC10 6432301 INFO/SYSTEM(VM) VERSION 3.1 | | 566432302 RC10 6432302 INFO/SYSTEM(VM) VERSION 3.1 | | 566432201 RC10 6432201 INFO/MMGT(VM) VERSION 3.1 | +--------------------------------------------------------------+ | 568505901 R202 HOZ4202 0521083 INFO/SYSTEM VERSION 4.2 | | 568505902 R202 HOX4202 0521084 INFO/SYSTEM DAS VERSION 4.2 | | 568506001 R202 HOY4202 0521073 INFO/MMGT VERSION 4.2 | | 568505901 R203 JOZ4203 0521073 VERSION 4.2 GRAPHICS FEATURE| | 568506001 R204 JOY4204 0521073 VERSION 4.2 (NET) FEATURE | | 568506001 R205 JOY4205 0521073 VERSION 4.2 (SAM) FEATURE | | 568506001 R206 JOY4206 0521073 VERSION 4.2 (OPC) FEATURE | | 568506001 R207 JOY4207 0521073 VERSION 4.2 (SLR) FEATURE | +--------------------------------------------------------------+ | 568505901 R222 HOZ4222 0521083 INFO/SYSTEM VERSION 4.2.2 | | 568505902 R222 HOX4222 0521084 INFO/SYSTEM DAS V4.2.2 | | 568505901 R290 JOZ4290 0521073 V4.2.2 Netview Bridge Adp. | +--------------------------------------------------------------+ | 569506500 R102 HOY5102 0562595 V5.1 Information Management | | 569517100 R101 HOY6101 0565381 V6.1 Information Management | +--------------------------------------------------------------+ | End of informational APAR. GT0405 | +--------------------------------------------------------------+
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
RALINFOAPAR
APAR Information
APAR number
II08364
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
1994-12-01
Closed date
1994-12-01
Last modified date
1994-12-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
01 December 1994