APAR status
Closed as canceled.
Error description
+--------------------------------------------------------------+ | Error description abstract: | | | | Problems with the Information/System-NetView Bridge | | Last updated: 07/11/95 MTG | +--------------------------------------------------------------+ | Detailed description of APAR: | | | | This informational APAR document several common problems and | | provides additional documentation resources. | | | +--------------------------------------------------------------+ | Publication references: | | There are several publications that users should have before | | attempting to use the bridge. You should have one of the | | following manuals based on your version and release of Info: | | | | o Netview Bridge Adapter Enablement Guide SC34-4464-0 for | | Version 6.1 Information/Management for MVS/ESA | | | | o The Information/Management Library NetView Bridge | | Adapter Reference Version 5, Release 1 for MVS/ESA | | SC34-4336-0 | | | | o The Information Family-NetView Bridge Adapter Version 4, | | Release 2 Modification 2 for MVS SC34-4318-0 | | | | The above NetView bridge books should be reviewed carefully | | and completely. They contain a practical REXX example in | | appendix E. | | | | Other useful manuals | | | | o Item 36244 (Document ID Q575856) on HONE or ServiceLink | | | | Practical, how to information with a REXX example. | | | | o Using the Information/System-NetView Bridge Adapter | | GG24-3734 Red book. | | | | The examples from this book are available softcopy. | | Contact your local IBM System Engineer and have them | | request INFOBR form MKTTOOLS. This red book should be | | reviewed carefully. It contains several complex REXX | | and C code examples. | | | | The following books based on you release of Info and NetView | | should be available for reference: | | | | o NetView Application Programmers Guide SC31-6098-0 V2 R2 | | | | o Info/Family Application Program Interfaces SC34-4187-1 | | V4 R2 | | | | o Application Program Interface Guide and Reference for | | Version 5, Release 1 for MVS/ESA SC34-4335-0 | | | | o Application Program Interface Guide and Reference | | Version 6, Release 1 for MVS/ESA SC34-4463-0 | | | | NOTE: Information/System V422 (HOZ4290) or higher and | | NetView Version 2 Release 1 or higher are required to use | | the Bridge. | | | +--------------------------------------------------------------+ | Technical information: | | | | | | This APAR is divided into two sections. The first section | | contains corrections to the documentation and the last | | section contains known problems experienced by Info and | | NetView Level 2. | | | +--------------------------------------------------------------+ | Use of APPLID parm on the EXEC card of PGM=BLGBSPC - The | | APPLID will be used to allocate data sets. It must be a | | valid high level qualifier for your system. Also the APPLID | | must be an user id in the Info privilege class name coded on | | the INFOBRDS Keyword 'INITCLAS.' | | | | INFOBRDS data set - The LRECL of the INFOBRDS data set must | | be 80 character fixed block, with a blocksize a multiple of | | 80. | | | | REXX example in appendix 'E' - The REXX example as stated is | | a practical one. It is only usable for a starting point, | | and it assumes that you have not modified your | | Info/Management panels. It will not work if you are using | | the Information Integration Facility (I/IF). The Bridge | | will work with I/IF; however, it will be necessary to create | | PIDTs based on the I/IF panels. See 'The Information\Family | | Application Program Interfaces manual SC34-4187-01 under | | User-Defined Record Support. | | | | IBRPRINT - The IBRPRINT data set must be a fixed sequential | | (FS) with a records length and block size of 104. You can | | not use SYSOUT for this data set. Refer to DD card IBRPRINT | | in the example JCL on page 2-2. | | | +--------------------------------------------------------------+ | Common problems: | | | | MSGBLG3003I ....... initialization of NetView bridge failed. | | Reason code is 1016. | | | | 'There was an attempt to initialize a server that was | | already active' according to the NetView Implementation | | manual. | | | | All 10xx return codes are PPI failures. The RC1016 in this | | case means that the RCVQUEUE name is not unique. RCVQUEUE | | is coded on the EXEC card of the JCL for PGM=BLGBSPC. This | | value can not match anything coded in NetView currently. | | When the bridge attempts to initialize it does a CNMETIN | | with this value. NetView checks all its tables for a value | | that matches. If NetView finds a value that matches it | | fails the CNMETIN with a return code 20 reason code 1016. | | RCVQUEUE MUST BE UNIQUE! | | | | MSGBLG3003I ....... initialization of NetView bridge failed. | | Reason code is 1026. | | | | This is another PPI failure to initialize. The RC1026 means | | 'The reviver program is not defined.' Not define could mean | | that it is not active. It will be active when the matching | | AUTOTASK is started. The AUTOTASK must be active before the | | Bridge is started. If the intended AUTOTASK is actually | | active before the bridge is started (NetView command "DSIBQL | | ALL" will display all queues. Active queues will have an | | asterisk '*'). Then the SEND_QUEUE value coded in the | | INFOBRDS does not match the oqueue value coded on the | | RTRINIT for the intended AUTOTASK. | | | | See the NetView Bridge Implementing (SC31-6033-1) Appendix | | C, page 144 for CNMETIN return codes. A better place to | | look is NetView Application Programming Guide SC31-6098-0 | | Appendix A, page 69. | | | | Running NetView/Info Bridge return code 2000 | | MSGIEF142I ....... SERVER1 -STEP WAS EXECUTED-COND CODE 2000 | | or | | MSGIBM534I ONCODE=8094 PROTECTION EXCEPTION | | AT OFFSET +0004EC IN PROCEDURE WITH ENTRY BLGBIAS | | | | See page 15 of Using the Information/System-NetView Bridge | | Adapter GG24-3734. The libraries in the STEPLIB are APF | | authorized, and should not be. | | | | MSGIBM818I ONCODE=1018 UNEXPECTED END OF FILE/STRING | | DETECTED IN STREAM INPUT. | | AT OFFSET +0004EC IN PROCEDURE WITH ENTRY BLGBIAS | | MSGBLG3001I TEC096P PL/I ON CONDITION 10 RAISED FOR DATA | | SET INFOBRDS | | | | Check the INFOBRDS data set. Make sure it does not contain | | sequence numbers in columns 72-80, and that is all | | uppercase. See above reference for more information. | | | | MSGIBM816I ONCODE=1016 UNABLE TO ALLOCATE THE IBRPRINT | | DATASET | | | | The IBRPRINT must be allocated with the following DCB | | information. | | | | DCB=(RECFM=F,LRECL=104,BLKSIZE=104) | | | | NOTE: DO NOT use SYSOUT for this data set! See above | | publication update. | | | | IBCREATE or IBUPDATE receive ERROR reply from module BLGBARY | | RESPCODE 10 REASON CODE 39. Page B-2 in the Using the | | Information/System-NetView Bridge Adapter manual says the | | RESPCODE 10 REASON CODE 39 'Text data length is not valid.' | | | | The length of the (free form) text passed can not exceed 132 | | characters. The manual will be updated. | | | | NetView AutoBridge (PID 5695-169) users only: | | ABEND047 in BLGBSPC when creating or updating Info records | | using the NetView AutoBridge | | | | This abend occurs when EYMSP010 issues SVC6B (modeset). | | Refer to the 'Autobridge Installation and User's Guide', | | p116, under STEP 2 'AUTHORIZE THE NETVIEW BRIDGE ADAPTOR | | CODE (BLGBSPC).' BLGBSPC must be relinked with AC(1). JCL | | to link BLGBSPC is shipped in BLMSAMP(Info V4.2.2) or | | SBLMSAMP(Info V5.1 and above) member BLGBSPCL. Add the | | SETCODE AC(1) for LMOD BLGBSPC. | | | | All NetView Bridge Adapter Users: | | ABEND047 in NetView when trying to start the INFO NetView | | Bridge Adapter. Please verify that the appropriate NetView | | maintenance is applied: | | PTF UW17584 for NetView R300 | | PTF UW17585 for NetView R400 | | The APAR chain is OW07432 then OW10775 then OW12915. | | | +--------------------------------------------------------------+ | 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. | | | | 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 V4 V422 ONCODE10 LVLS/101 | | LVLS/102 LVLS/222 LVLS/290 ONCODE1016 ONCODE1018 ONCODE8094 | | RC2000 CC2000 RC10 RC39 RIDS/BLGBARY MS/BLG3003I V51 V61 | | DATASET AB/S0047 ABENDS0047 | +--------------------------------------------------------------+ | Following are the components that apply to this APAR: | | COMPID REL FMID FESN PRODUCT DESCRIPTION | +--------------------------------------------------------------+ | 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 | +--------------------------------------------------------------+ | 568513801 R101 HVWW101 0521246 NETVIEW VERSION 2.1 MVS/XA | | 568511101 R101 HXYZ101 0521243 NETVIEW VERSION 2.1 MVS/ESA | | 568513801 R200 HVWW200 0521246 NETVIEW VERSION 2.2 MVS/XA | | 568511101 R200 HXYZ200 0521243 NETVIEW VERSION 2.2 MVS/ESA | +--------------------------------------------------------------+ | 569506500 R102 HOY5102 0562595 V5.1 Information Management | | 569517100 R101 HOY6101 0565381 V6.1 Information Management | +--------------------------------------------------------------+ | 569516900 R101 HPS5101 0564332 NetView AutoBridge | +--------------------------------------------------------------+ | End of informational APAR. GT0405 | +--------------------------------------------------------------+
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II05850
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1992-03-23
Closed date
1992-03-23
Last modified date
1995-07-11
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:
13 December 2020