CA-SORT, DFSORT, and SYNCSORT offer options to improve compatibility with CA EPIC for z/VSE. See the sort product's installation and configuration instructions for details about these options. See the Installation and System Guide for details about which SYNCSORT options to apply.
In addition, there are CA EPIC for z/VSE special options which must be applied for use with both sorts. See the Installation and System Guide, "Compatibility With Other Software" for details.
With these options activated, LUB allocation and secondary SORTWK allocations are supported, and SORTWK datasets are closed to allow them to be deleted. In addition, SYNCSORT can communicate directly with CA EPIC for z/VSE to allow truncation of disk output datasets, and to allow block/record sizes and counts to be stored in the DSN Catalog and on tape HDR2 labels.
CA-SORT, DFSORT, and SYNCSORT also use an improved type of pre-open checking which reduces the need for pre-open assignments, thereby simplifying JCL. Before checking assignments, these sorts access the VSE label area to determine whether the SORTINx and SORTOUT datasets are on tape or disk. If a matching disk or tape label is found, pre-open assignment checking is bypassed if the associated SYS number is assigned to a disk or tape device, or set to unassigned (UA). The sort then correctly assumes that CA EPIC for z/VSE will make the necessary assignment when the dataset is opened.
Recommendations:
If datasets that have been reblocked by CA EPIC for z/VSE will be read by a sort program, TSIDSRT must be executed if the block size specified in the sort control statement is incorrect.
If CA EPIC for z/VSE reblocking is not being used, SYNCSORT and CA SORT can be executed directly. However, CA SORT users may prefer to use TSIDSRT for disk output datasets to enable dataset truncation.
| Copyright © 2010 CA. All rights reserved. | Email CA Technologies about this topic |