A fix is available
APAR status
Closed as program error.
Error description
APPC/ASUITE ASUITE AFTP ACOPY APING APPCOPYE APPCOPYT APPFTPE APPFTPT APPPINGE APPPINGT The REXX execs to invoke ACOPY , APING or ACOPY do not have unique dataset naming conventions if run in batch mode (using the same userid on the job card). Allocation errors will result because of this. DATA SET USER1.ASUITE.APPFTPE.LOG ALREADY IN USE, TRY LATER DATA SET IS ALLOCATED TO ANOTHER JOB OR USER APPFTPE allocation error. RC=12
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All using AFTP and ACOPY * **************************************************************** * PROBLEM DESCRIPTION: Problems allocating trace and error log * * datasets when running ACOPY in batch * * mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running ACOPY from batch mode it allocates a dataset for the trace log and one for the error log. If multiple ACOPY jobs are run at the same time the dataset names will be identical and the allocations will fail. What is needed is a way to ensure that the dataset names for each ACOPY job are unique.
Problem conclusion
The ACOPY exec (APPFACMX) was modified to include the -r and -d parameters. Specifying -r causes the ACOPY exec to insert an extra data set qualifier in both the trace log and error log data set names. This extra qualifier will be A followed by six random digits. Specifying -d causes the ACOPY exec to delete the error log and trace log data sets if ACOPY completes with return code zero. The AFTP exec (APPFAFMX) was modified to include the -r parameter. Specifying -r causes the AFTP exec to insert an extra data set qualifier in both the trace log and error log data set names. This extra qualifier will be A followed by six random digits. The -d parameter was not added because the return code from AFTP is not meaningful and can not be used to determine if the data sets should be deleted. The following is a Request for Publication Change APPC Application Suite User's Guide SC31-6532-00 Page 55 ACOPY Format +- -t AFTPD---+ >--+-------------+--+-------------------------+-+------+--> +- -t tp_name-+ +- -n --------------------+ +- -r -+ +- -u userid -------------+ +- -u userid -p password--+ >--+------+--+------------+-------------------------------| +- -d -+ +- -l level -+ Page 57 -r Randomize the data set names for the error log and trace log. This is useful when running multiple ACOPY batch jobs to prevent data set allocation problems. (MVS Only) -d Delete the error log and trace log data sets if ACOPY completes with return code zero. (MVS only) Page 59 AFTP Format >--aftp--+---------------+-----+------+-------------->< +- -h ----------+ +- -r -+ +- destination -+ -r Randomize the data set names for the error log and trace log. This is useful when running multiple AFTP batch jobs to prevent data set allocation problems. (MVS Only)
Temporary fix
Comments
APAR Information
APAR number
OW19935
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
204
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1996-04-18
Closed date
1996-05-29
Last modified date
1996-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UW29323 UW29324 OW21818
Modules/Macros
APPFACMX APPFAFMX
| SC31653200 |
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
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":"204","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":"204","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 August 1996