APAR status
Closed as documentation error.
Error description
When users are configuring the ADABAS with the IBM Application Discovery Connect for Mainframe; On the LPAR where the ADABAS/NATURAL is installed, they are not able to find the members "ADAUT203 and AD203FIL" as instructed in IBM AD Connect for Mainframe Configuration Guide.
Local fix
ADAUT203 and AD203FIL are not members that we distribute. They represent fragments of JCL that we store in our INCLUDE libraries to represent the STEPLIB JCL cards and the ADA File DDNAME JCL cards that are unique to our ADABAS installation.
Problem summary
The configuration steps for Natural and Adabas were not clear to users.
Problem conclusion
New configuration steps for Natural and Adabas were added to the IBM Application Discovery Knowledge Center.
Temporary fix
Comments
APAR Information
APAR number
PH07704
Reported component name
AD MAINFRAME
Reported component ID
5737B1610
Reported release
510
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-01-24
Closed date
2019-05-21
Last modified date
2019-05-21
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":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRR9Q","label":"IBM Application Discovery for IBM Z"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
21 May 2019