A fix is available
APAR status
Closed as program error.
Error description
Using syslog browser panel EZABROWS to specify "Recall migrated data sets ==> NO" does not work as designed. Migrated data sets are still recalled with "NO" specified. Verification Steps: - verify migrated syslog log file pointed ot by syslog config file - Specify "Recall migrated data sets ==> NO" in EZABROWS panel - execute browser with syslog config file - message should appear that migrated data set is being recalled Additional Symptom(s) Search Keyword(s): NORECALL bpxwdyn recal archived
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release(s) 12 and 13 IP * * Syslogd Browser EZABROWS * **************************************************************** * PROBLEM DESCRIPTION: When the following EZABROWS migration * * option was specified migrated data sets * * were incorrectly recalled. * * "Recall migrated data sets ==> NO" * **************************************************************** * RECOMMENDATION: * **************************************************************** EZABROWS was using a REXX variable that was not available to its FindStart procedure. This caused incorrect logic to be executed that always caused migrated data sets to be recalled. +-------------------------------------------------------------+ + Please check our Communications Server for OS/390 homepages + + for common networking tips and fixes. The URL for these + + homepages can be found in Informational APAR II11334. + +-------------------------------------------------------------+
Problem conclusion
EZABROWS has been amended to correctly process the setting of its "Recall migrated data sets ==>" specification. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PM58651
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1C0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-21
Closed date
2012-03-12
Last modified date
2012-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK76987 UK76988
Modules/Macros
EZASYRGO
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"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":"1C0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1C0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 May 2012