APAR status
Closed as fixed if next.
Error description
Retrieving the CA-7 can be set to work in two ways from 'AD Build Configuration/Server': 'In memory' and 'Via dataset'. Due to the large amount of data to process that trigger a time-out, a '*' request was split by default in 29 requests (one for each alphabet letter and two special chars, e.g. : 'A*', 'B*', ...'Z*', etc). However when requesting data 'Via dataset' this field seems to be ignored by the MF agents (Calin still waited for a confirmation from Moshe on 30th of March 2018) and all the jobs configured on Mainframe (same ones) were returned for each request. That's why the duplication.
Local fix
This was fixed by not splitting a request anymore for 'Via dataset' mode for version 5.0.4.2. (30th March 2018 release).
Problem summary
**************************************************************** * USERS AFFECTED: Users of Build Server * Application Discovery Build Server **************************************************************** * PROBLEM DESCRIPTION: The customer (AirFrance) is stating that * the jobs submitted - approx ~27 - are duplicates of each * other, with the same input. These jobs were supposed to be * handling the sequential processing of the 'wildcard' * parameter. Customer is using the following parameters in the * submitted job, so we only process a subset of the CA7 job * estate: * /LOGON * LJOB,JOB=HRFZ*,LIST=ALL * /LOGOFF **************************************************************** * RECOMMENDATION: Apply Application Discovery 5.0.4.2 ****************************************************************
Problem conclusion
* PROBLEM DESCRIPTION: The customer (AirFrance) is stating that * the jobs submitted - approx ~27 - are duplicates of each * other, with the same input. These jobs were supposed to be * handling the sequential processing of the 'wildcard' * parameter. Customer is using the following parameters in the * submitted job, so we only process a subset of the CA7 job * estate: * /LOGON * LJOB,JOB=HRFZ*,LIST=ALL * /LOGOFF **************************************************************** * RECOMMENDATION: Apply Application Discovery 5.0.4.2
Temporary fix
N/A
Comments
APAR Information
APAR number
PI96023
Reported component name
AD MAINFRAME
Reported component ID
5737B1610
Reported release
504
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-03-30
Closed date
2018-04-02
Last modified date
2018-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SQLPAR
Fix information
Applicable component levels
R504 PSY
UP
[{"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":"504","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":"504","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
02 April 2018