Unicenter CA-Sort for VSE · and optimizes virtual storage management. ... CA-Sort in any programming language. ... (phases). Each part is loaded from the

Unicenter CA-Sort for VSE

Systems Programmer Guide 9.0

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2002 Computer Associates International, Inc. (CA)

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Chapter 1. Program Organization . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.2 Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Chapter 2. Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 The CASORT Option Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Chapter 3. SORTPARM - Overriding Unicenter CA-Sort Parameters . . . . . 3-13.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.2 Method of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.3 User Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.4 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Chapter 4. Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . 4-14.1 Optimization Aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.2 Main Storage Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.3 Unicenter CA-Sort Dataspace Support and the CA90PSTA Utility Program . . 4-9

Chapter 5. Running Unicenter CA-Sort Under CMS/DOS . . . . . . . . . . . . 5-15.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.2 Modifying Installation Options (CASORT Macro) . . . . . . . . . . . . . . . . 5-25.3 Displaying Unicenter CA-Sort Product Options (SRTCHECK Program) . . . . 5-35.4 Using Unicenter CA-Sort Under CMS/DOS . . . . . . . . . . . . . . . . . . . . 5-45.5 Executing Unicenter CA-Sort for CMS/DOS . . . . . . . . . . . . . . . . . . . . 5-65.6 Applying Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Chapter 6. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.2 Diagnostic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.3 Product Releases and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . 6-126.4 Requesting Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Contents iii

iv Unicenter CA-Sort Systems Programmer Guide

About This Guide

This guide serves as the primary reference for the Systems Programmer after UnicenterCA-Sort has been installed.

Organization of Manual

Chapter Description

1 Describes Unicenter CA-Sort sort/merge program organization.

2 Lists installation options and contains instructions for modifyingthem using the CASORT option macro.

3 Describes user exits, which allow you to modify the supplied codeto meet your data center's standards.

4 Covers performance considerations, optimization aids and mainstorage allocation.

5 Explains how to use Unicenter CA-Sort in a CMS/DOSenvironment.

6 Provides debugging methods and lists the information needed byComputer Associates to diagnose problems.

Index Provides a quick way to locate specific material.

About This Guide v

Summary of Revisions

Unicenter CA-Sort 9.0 allows the use of data spaces as work files. Users may now electto use data spaces instead of work files. This feature can be implemented using the newDSPSIZE parameter available on the CASORT macro and on the Unicenter CA-SortOPTION control statement.

vi Unicenter CA-Sort Systems Programmer Guide

Unicenter CA-Sort and Unicenter CA-SRAM Publications

In addition to this guide, the following publications are supplied with Unicenter CA-Sort:

All guides are updated as required. Instructions accompany each update package.Technical changes are identified by a revision bar (|) in the left margin. Revision barsare not used for editorial changes and new manuals.

Name Contents

Unicenter CA-Sort Installation Guide Installation procedure to installUnicenter CA-Sort

Unicenter CA-Sort User Guide Complete information on all ofUnicenter CA-Sort available to thegeneral user, and command syntax.

Unicenter CA-Sort/Unicenter CA-SRAMMessage Guide

Error messages and return codes. Foreach message an appropriate reasonand possible actions are listed.

Unicenter CA-SRAM User Guide Complete information on all ofUnicenter CA-SRAM available to thegeneral user, including commandsyntax.

Unicenter CA-SRAM Installation Guide Installation procedure to installUnicenter CA-SRAM.

Unicenter CA-SRAM SystemsProgrammer Guide

Planning, installation, and maintenanceprocedures.

About This Guide vii

Related Publications

The following publications relate to Unicenter CA-Sort and are available from ComputerAssociates:

■ CA-CIS documentation set

The following publications are not produced by Computer Associates but are referencedin this publication or recommended reading:

■ IBM's Using VSE/VSAM Commands And Macros■ IBM's Using VSE/VSAM Space Management For SAM■ IBM's VSE/ESA Data Management Concepts■ IBM's VSE/ESA Macro Reference■ IBM's VSE/ESA Macro Users Guide■ IBM's VSE/ESA System Management Guide■ IBM's VSE/ESA System Control Statements■ IBM's VSE/VSAM Programmer's Reference

viii Unicenter CA-Sort Systems Programmer Guide

Command Notation

Enter the following exactly as they appear in command descriptions:

The following clarify command syntax; do not type these as they appear:

UPPERCASE Identifies commands, keywords, keyword values andoperators which must be coded exactly as shown.

MIXed Cases Identifies command abbreviations. The uppercase lettersare the minimum abbreviation; lowercase letters areoptional.

Delimiters , ( ) = and blanks

lowercase Indicates keyword values which you must supply.

[ ] Identifies optional keywords.

{ } Requires choosing one of the keywords specified.

| Separates alternative keywords or values. Choose one.

... Means the preceding value may be repeated more thanonce.

Sample Command Explanation

SORT[WORK={n|DA}]

SORT is operator keyword.

WORK is optional operand.

You must either give a value for n or specify DA.

About This Guide ix

x Unicenter CA-Sort Systems Programmer Guide

Chapter 1. Program Organization

1.1 Overview

The Unicenter CA-Sort system is fully relocatable, may be executed in any VSE partitionand optimizes virtual storage management.

Initiation of Unicenter CA-Sort is under the user's control; execution may be started eitherby the EXEC job control statement in the application JCL, or by invoking UnicenterCA-Sort in any programming language.

Chapter 1. Program Organization 1-1

1.2 Phases

The Unicenter CA-Sort program consists of 4 parts (phases). Each part is loaded from thecore image library and adapted internally according to the sort/merge techniques definedby the user.

Phase 0 (Initialization and Optimization Phase)

Phase 0 will be executed in every SORT and MERGE execution. During this phase, theJCL and control statements submitted (or the parameter list for invoked sorts or merges)will be checked for errors in syntax or conflicts with system information. Error messageswill be printed on the printer and console if detected. In addition, the sorting environmentis checked carefully and, internally, execution variables and capacity estimates are madebased upon the CPU, storage available, disk devices on the system, and other similarfactors. In general, Unicenter CA-Sort optimizes itself to run most efficiently usinginformation gathered in this phase.

Phase 1 (Input and Internal Sorting Phase)

Phase 1 will be executed in every SORT execution. During this phase, the input files areopened and records are read and placed into sorted sequences called 'strings' in memory.A new string is begun when a record will not logically follow the previous record insequence. Whenever possible, Unicenter CA-Sort attempts to keep these strings entirelyin memory, thus avoiding the use of intermediate work files.

If there is not enough storage in the partition to contain all the strings, the work file isthen opened and the sorted sequences written to it. The creation of sorted strings from theinput data is the primary function of Phase 1.

Phase 2 (Intermediate Merge Phase)

Phase 2 will be performed only for SORT executions where the number of strings createdin Phase 1 is greater than the 'merge order.' Merge order is the maximum number ofstrings that may be combined at a time and is related to the amount of memory available.The main purpose of Phase 2 is to merge short strings into longer ones, thus reducing thetotal number of strings. Phase 2 will end when the number of strings remaining is lessthan the merge order and can be merged into a single string during the output phase.Small sorts normally skip this phase entirely.

Phase 3 (Final Merge and Output Phase)

Phase 3 is executed for every SORT and MERGE task. During this phase, the output fileis opened and the strings in memory or from the work files are combined in sequence toform a single sorted string, which is written to the output device.

1-2 Unicenter CA-Sort Systems Programmer Guide

Chapter 2. Installation Options

2.1 The CASORT Option Macro

To set generation defaults applicable to your installation, the CASORT option macro mustbe coded and assembled, following standard assembler language coding conventions.This macro will catalog a root phase under the name chosen in the PHASE= parameter,containing the generation options chosen. If a root phase name other than SORT ischosen, it must be renamed to be SORT before testing with COBOL programs whichinvoke the sort/merge package.

The following JCL is necessary to assemble the macro and recatalog the root phase.Omit the Assembler PRINT and COPY statements when using the DOS (for example,non-VSE) Assembler.

// JOB CASORT MACRO ASSEMBLY

// OPTION CATAL

// PAUSE LIB ASSGN/LIBDEFS IF NECESSARY

// EXEC ASSEMBLY

CASORT keyword parameters ...

END

/�

// EXEC LNKEDT

/&

Chapter 2. Installation Options 2-1

2.1.1 CASORT Keywords

The following keywords may be coded as operands in the CASORT macro:

Keyword Description

PHASE= Indicates the phase name to be given to the Unicenter CA-Sort rootphase. If the name SORT is not chosen, the root should berenamed to SORT manually.

Default = CA90SORT

Note: Either the default phase name or the name SORT must beused for the Unicenter CA-Sort root phase when executingCAISERV.

MODEL= Indicates the computer model on which Unicenter CA-Sort isinstalled. Use the table on page 2-16 to select the proper modelcode. Unicenter CA-Sort uses this value to determine theinstruction set to be used, and to obtain CPU timing estimates foroptimization purposes.

Default = 4331

OPT= Indicates the optimization and work file usage defaults as follows:

E The sort is to be optimized on the number of I/O accesses. Ifwork files must be opened, each extent for SORTWKn isopened sequentially as the previous one is filled. Theremaining work files and extents are opened only as needed.This is the preferred reply for multiprogramming orteleprocessing installations.

D The sort is to be optimized on CPU time, and open allextents on all work files if any work space is needed tospread I/O across volumes. This should be used only forsmall installations.

Default = E


Keyword Description

MSG= Indicates how runtime messages for JCL-initiated sorts (by theEXEC statement) are to be routed. The default may be overriddenusing the ROUTE= keyword on the OPTION control statement.

LST Runtime messages CASD201I-CASD599I will be routedto the printer whenever SYSLST has been assigned.

LOG Non-Phase 0 messages are to be routed to the operator'sconsole (SYSLOG).

BOTH Runtime messages CASD201I-CASD599I will be printedon both the printer (SYSLST) and the console(SYSLOG).

Default = LST

Notes on the MSG Parameter:

■ Runtime messages are those messages produced after Phase 0(during the actual sort/merge process). The preferred reply isLST because this response improves the performance of smallsort/merge tasks.

■ Runtime messages for program-invoked sorts are NOT affectedby this parameter, and will be routed to SYSLOG regardlessof the above response.

■ Phase 0 messages are NOT affected by this parameter and willbe directed to SYSLST regardless of the parameter specified.

■ If MSG=LOG or BOTH is specified, runtime messages willonly be directed to the console at end-of-job or if a fatalexecution error occurs.

JCLPRNT= Indicates which messages are to be printed for JCL initiated sorts(by the EXEC statement).

ALL All messages.

NONE No messages.

CRITICALOnly E level messages.

Default = ALL


Keyword Description

INVPRNT= Indicates which messages are to be printed for program invokedsorts.

ALL All messages.

NONE No messages.

CRITICALOnly E level messages.

Default = CRITICAL

PREOPEN= Indicates whether disk input files are to be opened in Phase 0 toobtain the CISIZE for FBA files from the VTOC or check for achange of device type between CKD and FBA.

YES This response should be coded if FBA disk devices arein use on the system, even if not used for sort files.

NO A mixture of CKD and FBA or all FBA devices doesnot exist in the installation. Disk input files will notbe opened in Phase 0 to check for a change in diskdevice type.

Default = NO

Users without a disk space management product must have alllogical units assigned before OPEN (except for VSAM/SAM inputand output files). Note that specifying of PREOPEN=YES,although acceptable, may introduce a small amount of unnecessaryoverhead. Any user with FBA devices should specify YES toensure that Unicenter CA-Sort can obtain the CISIZE necessary todeblock the input file or react dynamically to a change in devicetype between CKD and FBA devices.

PFIX= Indicates whether virtual pages are to be fixed in storage for betterperformance as follows:

YES Unicenter CA-Sort should attempt to page fix controlblocks and buffers up to the limit specified in thesupervisor ALLOCR operand for each partition. Aminimum of 6-8K real storage will be page fixedduring execution.

NO No page fixing or private CCW translation is to bedone.

Default = YES

YES is recommended on VSE to allow control blocks and I/Obuffers to be fixed and Private CCW Translation to occur forinput, output and work files. This will reduce supervisor overheadand paging. PFIX=YES is not allowed for non-VS systems.


Keyword Description

OPSYS= The operating system may be selected as one of the following:

VSE A VSE or compatible system is installed.

MVT A MVT/VSE system is installed. Unicenter CA-Sortrequires that the MVT parameter be coded whenrunning an MVT/VSE.

Default = VSE

STORAGE= Optional operand used to set a maximum limit on the use of mainstorage. The format is nnnnK.

Unicenter CA-Sort will not exceed the value specified in thisparameter unless overridden using the STORAGE keyword on theOPTION control statement. A reasonable limit is usually in therange 256K-512K.

Default = No limit

When determining the amount of main storage to use, UnicenterCA-Sort will first override the value specified in this operand witha value from the STORAGE= keyword on the OPTION controlstatement, if present. The result is then compared against thepartition size and the SIZE= parameter on the EXEC statement (orspace remaining in the partition, if invoked). The smallest of thesethree values is then set as the maximum storage limit for the run.

RESERVE= Optional operand specifying the minimal amount of partitionstorage to be reserved as a GETVIS area and not to be used bysort. The format is nnnnK.

Default = 128K


Keyword Description

DYNAMD= Indicates whether Unicenter CA-Sort is to interface to UnicenterCA-Dynam/D, as follows:

YES Unicenter CA-Dynam/D is installed and active. See'Unicenter CA-Sort and Unicenter CA-Dynam/DInterface' in the Unicenter CA-Sort User Guide for thefacilities provided by the Unicenter CA-Dynam/Dinterface.

NO Unicenter CA-Dynam/D is not installed and/oractivated.

Default = NO

If the interface has been enabled, either at generation time usingthis parameter, or at execution time with the OPTION controlstatement, Unicenter CA-Dynam/D must be active on the system.Failure to have Unicenter CA-Dynam/D active will cause everysort to cancel with the IBM message '4n80I INVALID FILETYPE'.

DYNAMFI= Indicates whether Unicenter CA-Sort is to interface to UnicenterCA-Dynam/FI, as follows:

NO Unicenter CA-Dynam/FI is not installed and activatedon the system.

YES Unicenter CA-Dynam/FI is installed and active. See'Unicenter CA-Sort and Unicenter CA-Dynam/FIInterface' in the Unicenter CA-Sort User Guide for thefacilities provided by the Unicenter CA-Dynam/FI.

Default = NO


Keyword Description

DEFDTF= Indicates the default DTF type to be built for the SORTINn andSORTOUT files if Unicenter CA-Sort cannot determine the propertype from labels or from existing assignments, as follows:

TAPE A tape DTF will be built if the logical unit has notbeen assigned correctly and labels were not submitted.

DISK A sequential CKD disk DTF will be built if the properdetermination cannot be made.

FBA Same as DISK, but an FBA DTF will be built.

CANCEL The default indicates the sort/merge is to terminate ifthe proper labels and/or assignments are not present.

Default = CANCEL

The DEFDTF value will only be used as a last resort to determinethe type of DTF to be built for input and output files. Typically,DTF determination will be made by the TLBL/DLBL statementfound in the job stream, with the logical unit assignment andDEFDTF values immaterial. Only if the logical unit is unassignedand a DLBL/TLBL was not found will the DEFDTF value takeeffect.

EQUALS= Indicates whether the EQUALS option is to be in effect by default,as follows:

YES Preserve the sequence of equally keyed input records.May degrade performance.

NO Records with equal keys may not be output in thesame sequence as they were read.

Default = NO


Keyword Description

CHECK= Indicates whether record counts should be checked at the end ofPhase 3 when an E35 exit is in use.

YES Record counts should be checked. If found to beunequal the message CASD207W will be issued. Thisis compatible with prior versions of UnicenterCA-Sort.

NO Unequal record counts will be accepted without error.

Default = YES

This parameter, which may be overridden using the OPTIONstatement, may be used to prevent abends caused by COBOLprograms which do not properly process all records in the OutputProcedure that were sorted in Phase 1. A 'Record Count Off'situation will be ignored only if CHECK=N is in effect and an E35exit has been specified (COBOL sorts always use an E35 exit).CHECK=Y is the recommended default to ensure output integrity.


Keyword Description

DISK= Indicates the DASD devices which may be used for sort workallocations. Unicenter CA-Sort uses the values specified in thisoperand to optimize the sort work block size chosen.

Specify one or more disk devices, in any combination, thatUnicenter CA-Sort should consider when performing Phase 0calculations for work block size. Do not specify devices which arenever used for sort work files. The allowable choices are 2311,2314, 3330, 3330-11, 3340, 3350, 3375, 3380, 3310, 3370, 3390and 9345. For FBA disk devices 93xx, specify 3370.

Default = None. Must be specified.

Specifying devices in this fashion means that users with a diskspace management product need not have the SORTWKn logicalunits preassigned to the proper devices, and the block size chosenby Unicenter CA-Sort will be of a size that will fit on any devicespecified in this parameter, thus allowing pooling of various DASDtypes. Because the work block size is based upon values in thistable and not the supervisor PUB table, a larger work block sizewill probably be chosen, resulting in fewer I/Os to the work files ifthe smaller capacity devices are not used for work files.

This parameter has no effect on SORTIN or SORTOUT devicetypes, and is only used for work file block size calculations. Thereare no checks made within Unicenter CA-Sort to ensure that awork file has been allocated on one of the devices specified in thistable.

Note: It is the user's responsibility to specify the allowable DASDtypes to ensure peak track utilization and performance, andto avoid I/O errors caused by writing a large block on asmall-capacity device not specified in the table.


Keyword Description

WKASN= Indicates whether Unicenter CA-Sort is to use the devices specifiedin the DISK= parameter or the DASD devices which are assignedto work file logical units when determining the optimum value forwork file block size. The allowable choices are:

OFF Use the disk devices which have been specified in theDISK= parameter.

ON Use only the devices which are assigned to work filelogical units.

Default = OFF

Unicenter CA-Sort is able to operate more efficiently when thetype of DASD devices which will actually be used for work fileallocations can be determined during Phase 0.

If a disk space management product is in use, especially in amixed DASD environment, the work file logical units may not bereliably assigned at execution time. In this case, WKASN=OFFshould be specified to allow block size calculations to be based onall devices which may be used for work file allocations. If theDISK= parameter has been specified correctly, all sorts will run,regardless of the devices used, but degraded performance mayresult if all specified devices are not used for work file allocations.

If correct assignments are normally provided for the work filelogical units, as is the case when running the IBM sort/mergeproduct, specifying WKASN=ON may provide better performanceby eliminating unused devices from the DISK= parameter andallowing a more optimum work file block size to be calculated.Only the DASD devices which are assigned to work file logicalunits will be used in block size calculations. WKASN=ON maybe used with a disk space manager only if the work file allocationsare made on one of the device types assigned.

The WKASN default setting may be overridden using the OPTIONcontrol statement. As is the case with the DISK= installationparameter, only work file block size calculations are affected bythe setting of the WKASN value.

INVCNCL= For program invoked sorts, indicates whether to pass a return codeor cancel the job when an error is encountered.

NO Transfer control to the calling program with a returncode.

YES Cancel the job.

Default = NO


Keyword Description

DYNALOC= Indicates whether work files will be allocated dynamically byUnicenter CA-Sort when no SORTWKn labels are defined for aUnicenter CA-Sort execution.

NO All work files are to be provided by the user.

vvvvvv,n Work files will be allocated dynamically duringUnicenter CA-Sort execution. DYNAMD=Y must bespecified and Unicenter CA-Dynam/D Release 5.3 orabove must be installed and active.

vvvvvv is required and may be 1-6 alphanumericcharacters, indicating where work file space will beallocated. It may be any valid DASD serial number, aUnicenter CA-Dynam/D generic volume serial numberor disk pool-ID.

n is optional. If specified, it must be in the range 1-9,indicating the number of work files to allocate. Ifomitted Unicenter CA-Sort will allocate 3 work files.

Examples:

DYNALOC=NO DYNALOC=(WORK01,2) DYNALOC=(WORK**)

Default = NO

RC= Sets return code at EOJ if VSE/SP 2.1 or above.

NO

Return code will not be set for use with conditionalJCL. Unicenter CA-Sort will CANCEL if errors.

YES Set return code to be used with conditional JCL.Unicenter CA-Sort will not cancel if errors.

0 Run Successful.

16 Errors occurred.

Default = YES

WKXTNTS= Indicates the maximum number of extents that may be allocatedfor SORT work files. Any value from 1 to 255 is valid.

Default = 25


Keyword Description

SPECIAL= A list of special options:

1. Force work=1.

2. EPIC compatibility for TLBL options and SORTWK deletion.

3. Do not close SYSPCH output (in order not to get an extrablank statement).

4. Ignore STORAGE= from the OPTION control statement forprogram invoked sorts.

5. Ignore STORAGE= from the OPTION control statement forJCL initiated sorts.

6. A default of FILES=1 for merge.

7. Optimize VSAM buffer space for files accessed by the optionFILNM parameter for improved performance. Requires thedefault reserve value to be increased by 55K for eachsimultaneously open option FILNM accessed file.

8. Always take DYNAM supplied record length.

9. Continuation statement options allow:

■ continued operands to start in positions 2 - 16.■ new operand and comments to start up to position 50.

10. Force PARAMS=SORTPARM (see SORTPARM).

11. Change errors CASD107E and CASD109E to warnings.

12. Allow VSAM record to be truncated to sort1(1) length toavoid a wrong length record error (7.2 compatibility).

13. Always display SORT summary record counts on SYSLOG.

14. Do not override the SORT INPFIL block size with the VSAMmaximum record length for VSAM/SAM undefined files.

15. Process invoked SORT runtime messages CASD201I andabove according to the MESSAGE= parameter of theUnicenter CA-Sort macro.

16. Always flag a long tape block as an error (messageCASD203E). Exit E18, exit E38, or bypass options may beused.

17. Version 1 tape DTF support for EPAT.


Keyword Description

ALTSEQ= Indicates a default alteration of the collating sequence for AQformat control fields. Every sequence definition must consist offour hexadecimal digits in the range of 0-9 or A-F.

ff represents the character whose position in the collatingsequence is to be changed.

tt represents the new position in the collating sequence thecharacter is to occupy.

Default = No alternate sequence. The EBCDIC collating sequenceis in effect.

The moved character (ff) is considered equal to the characteralready occupying the position to which the character is beingmoved (tt). The character in the tt position is not considered to bemoved, however, and it may have its sequence altered as an ffargument, if desired.

Control fields which have been defined using the AQ format codeare affected by the new collating sequence. If CHALT is in effect(see the CHALT generation parameter below or the CHALTkeyword in the OPTION control statement), control fields with theCH format code are also affected by the new sequence.

If ALTSEQ is not specified, all AQ control fields collate accordingto the standard EBCDIC sequence. An ALTSEQ control statementmay override any or all of the alterations specified in the CASORTgeneration macro ALTSEQ parameter.

CHALT= Indicates whether CH format control fields are affected by analternate collating sequence as in the case of AQ format controlfields. The CHALT generation parameter can be overridden by theCHALT or NOCHALT keywords in the OPTION controlstatement.

YES CH control fields collated by an alternate sequence.

NO CH control fields collated by the standard EBCDICsequence.

Default = NO


Keyword Description

Y2PAST= Specifies the type of century window (fixed or sliding) to be usedwhen interpreting 2-digit years. A century window spans a 100year period, such as 1950 to 2049, and determines how 2-digityears are handled. If the century window is set at 1950 to 2049,then a value of 60 would be interpreted as 1960. If the centurywindow is set at 1970 to 2069, a value of 60 would be interpretedas 2060.

F Specifies a fixed date at which the century window is tobegin. F can be any value between 1000 and 3000. If, forinstance, Y2PAST=1997, then the century window wouldbegin in 1997 and span from 1997 to 2096.

S Specifies the number of years before the current year that thecentury window is to begin. S can be any value between 0and 100. The default is 80. If, for example, the current yearis 1997, by default, the century window would begin at 1997- 80 or 1917. When the current year becomes 1998, thebeginning of the century window will change to 1998 - 80 or1918. In this case, the century window is now 1918 to2017.

| DSPSIZE=| Indicates the size, in megabytes, of the data space to be created. If| n is zero, no data space will be used. If MAX is specified, the size| of the created data space will be taken from the DSIZE of the| SYSDEF job control statement. The value of this parameter may| be overwritten through the DSPSIZE parameter of the OPTION| statement. The value of n must not exceen 2048.


Computer Model Codes

Machine Model Code Configuration

360/22360/25

25 All configurations

360/30 30 All configurations










370/155 155 With DAT feature

370/155 155 Without DAT feature



3031 3031 All configurations





other 30xx 3031 All configurations

ES9000 9000 All configurations








2.1.2 Sample Option Generation

The following example shows how typical generation options would be specified in theCASORT macro to generate a root phase for an installation running under VSE Release 2on a 4341 with a mixture of 3330, 3350 and FBA disks. Although the installationsimulates 2314 disks on FBA devices, these disks are never used for sort work files, and,as a result, are not coded in the DISK= operand of the CASORT macro.

// JOB CASORT OPTION MACRO ASSEMBLY

// OPTION CATAL

// EXEC ASSEMBLY

CASORT PHASE=SORT, .ROOT PHASE CALLED SORT �

MODEL=4341, .CPU IS A 4341 GROUP II �

OPSYS=DOSVSE, .DOS/VSE OPERATING SYSTEM �

STORAGE=3��K, .MAXIMUM STORAGE LIMIT �

RESERVE=128K, .MINIMUM STORAGE FOR GETVIS �

PFIX=YES, .PAGE FIXING IS ALLOWED �

OPT=E, .SEQUENTIAL WORK FILE OPENS �

DYNAMD=YES, .Unicenter CA-Dynam/D IS INSTALLED �

DYNAMFI=NO, .Unicenter CA-Dynam/FI IS NOT ACTIVE �

MSG=BOTH, .RUN MSGS TO SYSLST/SYSLOG �

JCLPRNT=ALL, .PRINT ALL FOR EXEC SORT �

INVPRNT=CRITICAL, .CRITICAL MSGS FOR INVOKED SORT �

PREOPEN=YES, .FBA DEVICES ARE IN USE �

DEFDTF=DISK, .DEFAULT DTF IS CKD DISK �

EQUALS=NO, .DO NOT SET EQUALS AS DEFAULT �

DYNALOC=NO, .DYNAMIC ALLOCATION OF WORK FILES�

RC=NO, .RETURN CODE AT EOJ �

SPECIAL=NONE, .NO SPECIAL OPTIONS �

INVCNCL=YES, .CANCEL ON ERROR FOR INVOKED SORT�

DISK=(333�-11,335�,337�), .MIX OF WORK DASD TYPES �

Y2PAST=8� .SLIDING CENTURY WINDOW SET �

| DSPSIZE=1�24 .DATA SPACE USAGE IS SET �

END

/�

// EXEC LNKEDT

/&


Chapter 3. SORTPARM - Overriding Unicenter CA-SortParameters

3.1 Overview

Due to the increasing complexity of job mixes found in today's data centers, it wouldoften be desirable to be able to override particular sort/merge parameters based uponspecific sets of criteria, such as time-of-day, paging rate, teleprocessing activity, and soforth. In the past, the only methods available were to use different sets of sort JCL basedon the shift, or have multiple copies of the sort with different generation parameters.

By using the SORTPARM exit, the user can interrogate the environment in a programand respecify a number of crucial parameters used by Unicenter CA-Sort so that it can betailored to meet each installation's specific needs. For example, SORTPARM could beused to:

■ Eliminate the need for the VOLUME= parameter on the INPFIL control statement,by requesting the operator to enter the correct number of reels, rather than changingthe sort control statements for each run.

■ Change the amount of storage the sort/merge is to use, based upon the shift, day ofthe week, number of active partitions, paging rate, CICS up, and so forth.

■ Change the message routing options from their generated defaults, or to correctcertain options given on outmoded JCL or invoked sorts.

■ Change the internal optimization schemes and work file usage patterns for certaincritical job streams or month-end processing.

■ Allow or disallow page fixing, based upon system load and amount of pages in thepage pool.

These are only examples of the types of flexibility the SORTPARM exit provides. Theuser may update the various options based upon any criteria that will make theinstallation run at peak efficiency.

Chapter 3. SORTPARM - Overriding Unicenter CA-Sort Parameters 3-1

3.2 Method of Operation

After the control statements for a JCL sort/merge or the parameter list passed from aninvoked program have been processed during Phase 0, a user program with the defaultphase name 'SORTPARM' is loaded into the partition and given control. User routineswith other phase names to perform different processing will be called by UnicenterCA-Sort if the name is specified in the control statements.

Upon entry to the SORTPARM routine, the address of the parameter list is pointed to bygeneral register 1. The values in the list represent the parameters currently in effect, seteither at generation time or by the control statements processed. These values may bemodified as needed, based upon any user criteria desired.

When control is given back to Unicenter CA-Sort, the control blocks within UnicenterCA-Sort will be updated to reflect any changes made, and Phase 0 processing willcontinue, using the new values. Parameters not modified by the user will retain the samevalues as presented to the routine.

To cause the user program to be loaded and executed, either form of the followingparameter may be placed on the OPTION control statement:

PARAMS or PARAMS=name

where 'name' represents a 1- to 8-character phase name of the routine to be loaded. If noname is specified, the default phase SORTPARM will be loaded. Although only one userroutine will be loaded by Unicenter CA-Sort per sort/merge execution, the ability tospecify a phase name allows multiple routines to be coded and executed based upon thetype of processing being performed.

Example:

OPTION PRINT=ALL,PARAMS

OPTION ROUTE=LST,PARAMS=PAYROLL

The SORTPARM routine may be written in either Assembler language or COBOL.


3.3 User Considerations

Upon entry, general registers 1, 13, 14 and 15 will be set by Unicenter CA-Sort accordingto VSE linkage conventions to contain the address pointers below. All registers should besaved upon entry to SORTPARM and restored before exiting using the SAVE andRETURN macros.

If any subroutines or LIOCS modules are used in the user routine, it is the user'sresponsibility to provide a separate register save area within SORTPARM, save register13 upon entry, and load the address of the new save area into register 13. Before exitingand restoring the registers used by Unicenter CA-Sort, register 13 must be reloaded withthe saved value.

The SORTPARM exit must not be linked as nonrelocatable. Self-relocating or relocatableexits may be used (S,*, or +0 on the PHASE statement). The use of the SORTPARM exitdoes not affect the operation of any other exits being used.

Sufficient storage must be available in the partition in excess of the 30K minimumstorage requirement of Unicenter CA-Sort, in order to load the user routine. An 'OP77ICANCELLED DUE TO INVALID ADDRESS' will result if there is not.

The SORTPARM exit will be activated after the control statements (or parameter list forinvoked sorts) have been processed and, therefore, any value reset through the use of thisexit routine will override any options specified on control statements.

Register Contents

1 Address of the parameter list.

13 A save area in which to save, upon entry, the registers used byUnicenter CA-Sort.

14 Return address within Unicenter CA-Sort.

15 Entry point of the 'SORTPARM' user routine.


3.4 Examples

3.4.1.1 Example 1

Assembler language DSECT showing the parameters passed to a user SORTPARMroutine for modification. The number to the left of each entry is the displacement inhexadecimal from the beginning of the parameter table for each value which may bemodified.

PARMLIST DSECT

�� PLSTOR DS F .STORAGE TO BE USED IN BYTES

��4 PLPRNT DS C .MESSAGES - ALL

PALL EQU C'A' ALL

PNONE EQU C'N' NONE

PCRIT EQU C'C' CRITICAL

��5 PLRUN DS C .MESSAGES - RUN-TIME ONLY

RMLST EQU C'L' LST

RMLOG EQU C'C' LOG (CONSOLE)

RMBOTH EQU C'B' LAL (BOTH)

��6 PLROUT DS C .ROUTE PARAMETER

RLST EQU C'L' LST

RLOG EQU C'C' LOG (CONSOLE)

RBOTH EQU C'B' LAL (BOTH)

RDEF EQU C'D' PH�=LST, RUN PER MACRO

��7 PLOPT DS C .OPTIMIZATION AND WORK-FILE USE

OPTE EQU C'E' E AND SEQ WF USAGE

OPTD EQU C'D' D AND SIMUL WF USAGE

��8 PLDTF DS C .DEFAULT DTF TYPE

TAPE EQU C'T' TAPE

DISK EQU C'D' DISK

FBA EQU C'F' FBA

CANCEL EQU C'C' CANCEL

��9 PLEQ DS C .EQUALS OPTION

EQ EQU C'E' EQUALS (MAY DEGRADE PERF)

NOEQ EQU C'N' NOEQUALS

��A PLDYND DS C .Unicenter CA-Dynam/D INTERFACE

DYND EQU C'Y' ENABLED

NODYND EQU C'N' DISABLED

��B PLPFIX DS C .SHOULD PFIXING BE USED

PFIXY EQU C'Y' YES

PFIXN EQU C'N' NO

��C PLVOL DS XL9 .NBR OF UNLABELED INPUT VOLUMES

LOGUNIT DS �XL2� .LOGICAL UNIT DEFAULTS

�15 PLLUOUT DS XL1 SORTOUT - X'FF' = NOT USED

�16 PLLUIN DS XL9 SORTIN1-SORTIN9 - X'FF'=NU

�1F PLLUWK DS XL9 SORTWK1-SORTWK9 - X'FF'=NU

�28 PLLUK DS XL1 SORTCKP

PLLEN C EQU �-PARMLIST .LENGTH OF PARMLIST = X'29' = 41


3.4.1.2 Example 2

COBOL linkage section showing the parameters passed to a user SORTPARM routine formodification.

�1 PARMLIST SYNCHRONIZED.

�5 PL-STORAGE PIC S9(8) COMPUTATIONAL.

�5 PL-PRINT PIC X.

88 PRINT-ALL VALUE 'A'.

88 PRINT-NONE VALUE 'N'.

88 PRINT-CRITICAL VALUE 'C'.

�5 PL-RUN-MSGS PIC X.

88 RM-LST VALUE 'L'.

88 RM-LOG VALUE 'C'.

88 RM-BOTH VALUE 'B'.

�5 PL-ROUTE PIC X.

88 ROUTE-LST VALUE 'L'.

88 ROUTE-LOG VALUE 'C'.

88 ROUTE-BOTH VALUE 'B'.

88 ROUTE-DEFAULT VALUE 'D'.

�5 PL-OPT PIC X.

88 OPT-E VALUE 'E'.

88 OPT-E VALUE 'D'.

�5 PL-DEF-DTF PIC X.

88 DTF-TAPE VALUE 'T'.

88 DTF-DISK VALUE 'D'.

88 DTF-FBA VALUE 'F'.

88 DTF-CANCEL VALUE 'C'.

�5 PL-EQUALS PIC X.

88 SET-EQUALS VALUE 'E'.

88 SET-NOEQUALS VALUE 'N'.

�5 PL-DYNAMD PIC X.

88 DYNAMD-YES VALUE 'Y'.

88 DYNAMD-NO VALUE 'N'.

�5 PL-PFIX PIX X.

88 SET-PFIX VALUE 'Y'.

88 SET-NOPFIX VALUE 'N'.

�5 PL-INPUT-VOLCNT OCCURS 9 TIMES.

1� NBR-OF-VOLS PIC X.

�5 PL-LOGICAL-UNITS.

1� OUTPUT-LU-DEFAULT PIC X.

88 NO-DEFAULT-LU VALUE HIGH-VALUES.

1� INPUT-LOG-UNITS OCCURS 9 TIMES.

15 INPUT-LU-DEFAULT PIC X.

1� WORK-LOG-UNITS OCCURS 9 TIMES.

15 WORK-LU-DEFAULT PIC X.

1� CHKPT-LU-DEFAULT PIC X.


3.4.1.3 Example 3

Sample SORTPARM exit to set the storage used to 100K from 6:00 AM to 6:00 PM, andreset it to 150K during the night hours of 6:00 PM until 6:00 AM.

SORTPARM START �

USING SORTPARM,15 .ESTABLISH ADDRESSABILITY

SORTSTRT SAVE (14,12) .SAVE Unicenter CA-Sort'S REGISTERS

DROP 15 .MIGHT BE USED BY DOS/VS MACROS

USING SORTSTRT,12 .DECLARE A NEW BASE REGISTER

LR 12,15 .LOAD IT FROM OLD BASE REG

L 2,�(,1) .REG 2 = ADDR OF PARAM LIST NOW

ST 13,SAVER13 .SAVE PTR TO SAVE AREA

�

GETIME STANDARD .OBTAIN TIME IN HHMMSS

ST 1,CURTIME .SAVE CURRENT TIME

CP CURTIME,SIXAM .IS IT BEFORE 6:�� AM ?

BNH NIGHTME .YES, SET HIGH STORAGE

CP CURTIME,SIXPM .IS IT BEFORE 6:�� PM ?

BL DAYTIME .YES, SET LOW STORAGE

NIGHTME EQU �

L 3,C15�K .USE STORAGE=15�K AT NIGHT

ST 3,�(,2) .STORE IN STORAGE SLOT IN PLIST

B RETRN .RETURN TO Unicenter CA-Sort

DAYTIME EQU �

L 3,C1��K .ELSE USE 1��K MAX ON FIRST SHIFT

ST 3,�(,2) .STORE IN STORAGE SLOT IN PLIST

RETRN EQU �

L 13,SAVER13 .RESTORE SAVE AREA ADDRESS

RETURN (14,12) .RESTORE REGS AND RETURN

�

SAVER13 DS F .HOLD FOR SAVE AREA ADDRESS

CURTIME DS PL4 .HOLD FOR CURRENT TIME

SIXAM DC PL4'�6��' .CONSTANT 6:��:�� (6:�� AM)

SIXPM DC PL4'18��' .CONSTANT 18:��:�� (6:�� PM)

C1��K DC F'1�24��' .CONSTANT 1��K FOR DAY USE

C15�K DC F'1536��' .CONSTANT 15�K FOR NIGHT USE

LTORG

END SORTPARM


Chapter 4. Performance Considerations

4.1 Optimization Aids

The following basic rules should be followed in order to achieve optimum performance:

■ Disk work space definition

Unicenter CA-Sort uses a very limited amount of external work space on disk. Itonly needs a work space size (expressed in tracks) corresponding to the sort input filevolume (plus a reserve of some 10percent). Typically, the IBM sort systems requirean increase of between 25 percent and 100 percent.

The amount of Unicenter CA-Sort disk work space may be considerably reduced toachieve the same (or comparable) maximum sort capacity possible with the IBM sort.The space which becomes free may be assigned to other programs. The necessaryamount of work space tracks for Unicenter CA-Sort should be determined by usingthe ANALYZE statement which gives worst-case space estimation (for example, withenough reserves for a different distribution of records).

The amount calculated may be used for subsequent sort executions only if thefollowing conditions apply:

– same input file size– same main storage size– file size estimation has been specified on the SORT statement

■ File size estimation

The file size estimation (SIZE=parameter on the SORT statement) has influence onthe total sort performance. It should show, whenever possible, the expected numberof input records or, at least, the maximum number of records which may beprocessed. The estimated value should never be lower than the actual file size. Inorder to achieve comparable working environments, the work space definition shouldbe recalculated using the method described above.

Chapter 4. Performance Considerations 4-1

■ Optimization parameters

Depending on the requirements of a particular installation, Unicenter CA-Sort may becustomized either to:

– reduce the elapsed and CPU time– reduce the total number of I/O accesses

In all cases, Unicenter CA-Sort tries to reduce the total system utilization. With theabove two options, priority may be given to one factor.

OPT=D ("dedicated") optimizes elapsed and CPU time when the sort time itself is acritical factor (for example, large sorts which occupy the whole machine) or whenthe CPU utilization is to be reduced. This option is to be preferred when systemtiming and/or comparison measurements are to be performed.

OPT=E ("EXCP") optimizes the number of I/O accesses and should be used whenthe total multiprogramming throughput is to be increased, or for systems with heavyteleprocessing activity. This is the recommended default optimization value.

The OPT= keyword may be defined on the OPTION control statement.

Example:

OPTION PRINT=ALL,OPT=E

The default OPT value is set during Unicenter CA-Sort installation. This value isshown on the first line printed by Unicenter CA-Sort:

CASD��I SORT FIELDS=(.... �yymmSD��,E�

↑ ↑

installed genlevel ----------+ |

|

optimization default=E -----------------------+

The success of the different optimization schemes is dependent on meaningful fileestimation (SIZE= parameter on the SORT control statement).


■ BIAS factor

The BIAS value is a measure of string length to work space usage and indicates theavailability of preordered sequences in the sort input file. Its range is between:

100 - file ordered in reverse sequence150 - file is in random order (default value)

15000 - file is already ordered in the desired sequence.

The actual bias value is printed by the Unicenter CA-Sort message:

CASD210I END SORT PH, BIAS=xxxxx

Whenever the actual value differs substantially from the default value of 150 (forexample, being more than 300-400) it may be specified for the subsequent sort runon the SORT statement as follows:

SORT FIELDS=(10,5,BI,A),WORK=1,BIAS=320

Improved sort performance may result if the BIAS factor is periodically adapted forcritical sorts. The BIAS factor has little or no influence in small sorts.

An in-core sort uses no work space, making the BIAS value meaningless. If anin-core sort was performed, BIAS=NA will be printed, indicating the bias value was"not available."


■ Optimization for variable-length record sorts

The performance of sorting applications using variable-length records is dependentupon the correct specification of the modal record length. The modal record lengthdescribes the length of the most frequent record in the file. It may also beapproximated by the average record length. The average record length isautomatically calculated by Unicenter CA-Sort and printed. For subsequent runs thisvalue may be defined as the l5 parameter on the RECORD statement. Considerabletime savings will result from a correct l5 specification.

Example of optimization:

Run Number 1

// JOB.......

:

:

// EXEC SORT

CASD��I SORT FIELDS=(........

CASD��I RECORD TYPE=V,LENGTH=2��

:

:

CASD�32I L5=1�� assumed l5 default

CASD21�I END SORT PH, BIAS=18�

CASD214I AVERAGE RL=��12� actual value (large difference

| against the assumed l5)

|

|

Run Nbr 2 |

// JOB....... +-----------------+

: |

: |

// EXEC SORT |

CASD��I SORT FIELDS=(.... ↓

CASD��I RECORD TYPE=V,LENGTH=(2��,,,,12�)

:

:

:


4.2 Main Storage Calculations

Allocation of main storage to the sort/merge execution can be the most important factorinfluencing execution and performance. As more storage is allocated, performancegenerally improves.

Minimum main storage factors are presented first, followed by some general guidelinesfor specifying optimum storage values.

4.2.1 Minimum Main Storage

The minimum main storage required by Unicenter CA-Sort is 30K bytes. However, for agiven sort operation, the minimum main storage required can be greater than 30K bytes.As a rule, the minimum main storage size can be calculated as the sum of the following:

■ Main storage for Unicenter CA-Sort modules and control blocks. This is alwaysrequired. The storage size estimate is 8K if the Unicenter CA-Sort runtime phases areinstalled in the SVA. If phases are not in the SVA, an additional 10K should beadded.

■ Main storage for execution-time generated routines to handle control field extraction,comparison, record selection, reformatting, and so forth. The storage requireddepends on the number and format of the control fields and the logical relationsspecified in the SORT/MERGE, INCLUDE/OMIT, SUM, INREC, and OUTRECcontrol statements. In general, these routines will not exceed 4K.

■ Main storage for input/output file DTF (100 bytes) and at least one input/outputbuffer. The size estimate for the buffer is the larger of either the maximum input oroutput block size, plus 8 bytes. For FBA input and output files, the file CISIZEinstead of BLKSIZE should be used in calculating the buffer size.

For VS files, SUM, INREC, and OUTREC processings, an additional recordassembly area of maximum logical record length is required for each of the facilitiesspecified.

■ Main storage for user-written exit routines. This is the largest of PH1, PH2, or PH3exit phase length, unless the phases are preloaded. The amount of storage reserved byUnicenter CA-Sort for each PHn exit will be the larger of the value specified in thelength parameter of the MODS control statement, or as determined from the coreimage library directory entry for the phase length. For further description of thestorage management techniques used by Unicenter CA-Sort, refer to the MODScontrol statement in the Unicenter CA-Sort User Guide.


■ Main storage used for sorting. There must be enough storage to hold at least fourinternal records plus two sort work buffers. Internal record length is usually equal tothe input record length, E15-modified input record length, or the record length afterINREC processing, plus 4 rounded up to a multiple of fullwords. An additional 4bytes is required for each record when the EQUALS option is in effect. The sortwork buffer size used should be the larger of the internal record length plus 16 bytesor the minimum block size for the work file device type.

The minimum block sizes for work file device types is as follows:

The result of the total main storage size should be rounded up to the next multiple of4K (for example, 66K yields 68K). This will allow for the additional overhead inpage-boundary alignment, CCWs, IDALs, and so forth.

Device Type Minimum Block Size

2311 700

2314 940

3330 MOD 1 1760

3330 MOD 11 1760

3340 1080

3350 2800

3375 3000

3380 6356

3390 6356

3310 2040

3370 4600

93xx 4600


4.2.2 Optimum Main Storage

The minimum storage value allows for the Unicenter CA-Sort modules and a minimumnumber of buffers to be allocated for most record and block sizes. This minimum valueis, of course, not the optimum storage value. When storage size is restricted, sort/mergeperformance decreases due to increased I/O activity. Increasing storage allocations abovethe minimum will tend to increase the sort work block size, thereby decreasing theamount of I/O performed. Increasing storage is recommended for every sort/mergeexecution to maximize performance. Most sort/merge executions may be performedefficiently when 150K-250K of storage is available to the package.

The following figure illustrates how adding main storage can affect performance in apositive manner, by overcoming the effects of fixed overhead and small block sizes:

+-------------------------+ +--------------------------+

| | | |

| Control Blocks and | | Control Blocks and |

| Module Storage | | Module Storage |

| | | |

+-------------------------+ +--------------------------+

| | | |

| 2 I/O Buffers | | |

| | | |

+-------------------------+ | |

Storage=4�K | |

| 1� I/O Buffers |

| |

| |

| |

| |

| |

+--------------------------+

Storage=8�K

Although the above example is only for illustrative purposes, it is evident that increasingthe main storage available provides the most benefit in the area of I/O buffers. In theexample, by doubling the amount of storage, only one-fifth the amount of I/O will beperformed. This saving will be demonstrated in lower EXCP counts and CPU time.

Storage should be allocated as high as possible to allow more sorts to be performedin-core, and those that cannot, to produce fewer strings and issue less I/O operations.When modules are loaded into the Shared Virtual Area under VSE, less storage isoccupied by executable code and more of the partition is made available for sortingrecords.


The amount of main storage used by the sort/merge program is a critical factor in theperformance of the whole VSE installation. Unicenter CA-Sort adapts itself automaticallyto the available main storage space depending on the real portion of the sort partition andthe size of the main page pool. The calculated size may change based on the totalcomputer load. Both Unicenter CA-Sort and the IBM 5746-SM1 sort print the storagesize used in the SYSLST messages:

Unicenter CA-Sort

:

:

:

:

CASD�71I STORAGE USED=nnnnn

IBM

:

:

:

:

7�84I STORAGE USED=nnnnn

The storage space may be determined by the SIZE= parameter on the EXEC SORTstatement or the STORAGE parameter on the OPTION control statement. Under VSE,care must be taken to ensure that the amount of virtual storage allocated to the sortpartition does not greatly exceed the amount of real storage available in the page pool.Excessive paging and/or deactivation could occur as a result, causing a degradation ofperformance. Excessive use of storage may be avoided by specifying a limiting value inthe STORAGE parameter of the CASORT installation macro.

Unicenter CA-Sort will always limit the amount of storage to the smallest of any of thefollowing:

■ generation default

■ STORAGE value on OPTION control statement

■ SIZE on EXEC statement

■ partition size.

If a default was set at generation time using the STORAGE operand of the CASORTmacro, the storage to be used can never be increased above this limit, except through theuse of the STORAGE operand on the OPTION control statement, or a value set by aSORTPARM user exit.

The limit specified in the CASORT macro should be based on the processor load andpaging activity to minimize the impact on other active partitions.


4.3 Unicenter CA-Sort Dataspace Support and the CA90PSTAUtility Program

In order to improve performance, all Unicenter CA-Sort phases are being moved into adataspace at CA-System Adapter intialization, by the execution of a new utility programcalled CA90PSTA. This program eliminates all Unicenter CA-Sort phase search and loadoperations.

CA90PSTA requires approximately 256K of dataspace. If your installation is alreadyusing dataspaces, add 256 to the 'DSIZE=' parameter of the SYSDEF DSPACE on yoursystem and allow for one more dataspace in the 'MAX=' parameter. If there are nodataspaces defined in your system, add the following command to your asi proc, to beexecuted in the BG partition:

SYSDEF DSPACE,DSIZE=256K

Be aware that if Unicenter CA-Sort SVA eligible phases are loaded in the SVA, theymust be loaded prior to CASAUTIL execution.

Warning: If the SVA is reloaded or a PTF is applied to any of the Unicenter CA-Sortphases, then CA90PSTA must be re-executed.



Chapter 5. Running Unicenter CA-Sort UnderCMS/DOS

5.1 Overview

Unicenter CA-Sort is capable of operating in a CMS/DOS environment under VM/SP.Using Unicenter CA-Sort, input files may consist of any mixture of CMS, DOS SAM,VSAM or tape files, with the output file being directed to CMS, VSAM or tape. Spacefor sort work files will be allocated as CMS files.

Due to the restrictions of CMS/DOS, many of the Phase 0 assignment restrictions whichwere removed or relaxed when running under DOS/VS or VSE, are restored. Logicalunits must be preassigned and label records must be properly defined before beginningthe Sort/Merge process.

To assist in this effort, Unicenter CA-Sort for CMS/DOS provides several CMS EXECsto set up the necessary DLBL and ASSGN control statements for CMS/DOS. A completelist of the CASDOS EXEC messages is included in the Message Guide, specificallymessages CASD601A - CASD657E. In addition, a CMS HELP file is supplied toprovide a quick reference in the operation of the EXEC.

Unicenter CA-Sort may be initiated by using the EXEC procedure, by invoking it fromanother program, or by submitting the necessary CMS/DOS job control statementsmanually.

Chapter 5. Running Unicenter CA-Sort Under CMS/DOS 5-1

5.2 Modifying Installation Options (CASORT Macro)

Although most installations will find the Computer Associates supplied defaults adequate,follow the steps listed below to change the default installation options using the CASORTmacro:

1. Execute CACMSALT, select SDSORT, and change the parameters as required. FileCA72A000 ASSEMBLE calls the CASORT macro and contains the default optionsshown below. (For more information on installation options, refer to the "InstallationsOptions" chapter of this manual.)

CA72A�� CASORT , -

MODEL=4331, MODEL IS 4331 -

MSG=BOTH, ROUTE MESSAGES TO SYSLST AND SYSLST -

OPT=E, SEQUENTIAL WORK FILE USAGE -

DYNAMD=NO, Unicenter CA-Dynam/D DOES NOT EXIST IN CMS/DOS -

DEFDTF=CANCEL, USER MUST SUPPLY DLBL/ASSGN FOR CMS/DOS -

PREOPEN=NO, DO NOT OPEN INPUT IN PHASE � -

OPSYS=DOSVSE DOSVSE OPERATING SYSTEM -

END

2. When all changes have been made, enter FILE to terminate edit processing.

3. When prompted, enter GO to assemble CA72A000. If this step completessuccessfully, CASDSORT DOSLIB will be recreated using the installation EXECCASRDGEN.

4. After verification of successful installation, move the new DOSLIB to its permanentlocation.


5.3 Displaying Unicenter CA-Sort Product Options(SRTCHECK Program)

Follow the steps below to display the Unicenter CA-Sort options currently in effect forCMS/DOS:

1. Access the Unicenter CA-Sort DOSLIB by entering

GLOBAL DOSLIB CASDSORT

2. Activate the CMS/DOS environment by entering the CMS command

SET DOS ON

3. Run the SRTCHECK program by entering

FETCH SRTCHECK (START

The output displayed on the screen by SRTCHECK indicates all Unicenter CA-Sortoptions currently in effect.

For example:

EXECUTION BEGINS...

CASD7��I Unicenter CA-Sort CMS/DOS VERSION 7.2 GENERATION OPTIONS IN EFFECT

CASD7�1I GENLVL= 86�8SD��

CASD7�2I PACKAGE PREFIX= CA72

CASD7�3I SYSTEM INSTR SET= 37�/43��

CASD7�4I MODEL CLASS= 4341

CASD7�5I OPSYS= DOS/VS(E)

CASD7�6I MSG= BOTH

CASD7�7I PFIX= YES

CASD7�8I OPT= E

CASD7�9I DYNAM/D= NO

CASD71�I STORAGE= 4��K

CASD715I PREOPEN= NO

CASD711I DEFDTF= CANCEL


5.4 Using Unicenter CA-Sort Under CMS/DOS

Some Unicenter CA-Sort functions which are available when executing under VSE arenot available in a CMS/DOS environment. These include:

■ DOS SAM files may not be specified for output, due to CMS/DOS restrictions.Output files may, however, be tape, CMS or VSAM files.

■ CMS/DOS and VM/SP do not support VSAM-managed SAM files.

■ Although PFIX=YES will be accepted by the CASORT option macro, page fixing isignored under CMS/DOS.

■ CMS/DOS requires that all ASSGN and DLBL/LABELDEF statements be in effectbefore beginning the Sort/Merge process. Use of the CASDOS EXEC will simplifythis process.

■ Unless Unicenter CA-Sort is initiated from another program, the sort/merge controlstatements must be placed in a fixed-length, 80-byte CMS file. This file must beidentified to Unicenter CA-Sort using a DLBL for IJSYSIN and ASSGN to SYSIPT.

■ The INPFIL/OUTFIL control statement is ignored unless a DOS simulated file (forexample, with a filemode of 4) is being read or written. These types of files aregenerally created in simulated VSE format by executing a program which containsstandard VSE SAM macros (DTFSD/GET/PUT, and so forth) in a CMS/DOSenvironment. DOS format files may be mixed with CMS format files for input and/oroutput.

■ Any file with a filemode other than 4 will be treated as a standard CMS format file.

■ CMS files with a filemode other than 4 containing variable-length records are notstored with RDWs. However, when Unicenter CA-Sort reads these files, an RDW isbuilt for each record. The Record Descriptor Word is stripped before writing to aCMS variable-length record file. When specifying Sort/Merge control fields, thefour-byte RDW must be taken into account.

■ Unicenter CA-SRAM and Unicenter CA-Dynam are not supported under CMS/DOS.The string-merge sorting technique will always be used in CMS/DOS.


The following control statements and keywords are not supported in a CMS/DOSenvironment:

■ The INREC control statement may not be used.

■ The CHKPT|CKPT keyword on the SORT control statement will be ignored.Checkpoints are not supported.

■ The WORK=DA parameter on the SORT control statement has no meaning in aCMS/DOS environment. If specified, WORK=1 will be assumed by UnicenterCA-Sort.

■ The following INPFIL statement keywords are not supported: ISAM, DATA,BUFOFF, and SYSIPT. CMS/DOS does not support ISAM files or ASCII input.

■ The following OUTFIL statement keywords are not supported: SYSLST, PUNCH,PCHLST, TITLE, DUMP, CHAR, HEX, LIST, CADART, SPAN, and BUFOFF.

■ The following OPTION statement keywords may not be specified: CASCADE,DYNAMD, DYNAMFI, PREOPEN, SKIPREC, NRECS, VERIFY, NOVERIFY, andNOERASE. ADDROUT may be used with VSAM input files only.


5.5 Executing Unicenter CA-Sort for CMS/DOS

Unicenter CA-Sort may be executed using any of three methods under CMS/DOS. Theseinclude:

■ the CASDOS EXEC

■ the CMS FETCH command

■ invoking from another program.

Sort/Merge messages will be directed to the SYSLST logical unit. If it is desirable toview these messages, an ASSGN statement should be issued. If SYSLST will be directedto a CMS file, a DLBL statement will also be required for the file name IJSYSLS.Messages may be sent to the printer if an ASSGN has been issued to that device. IfUnicenter CA-Sort has been invoked from another program, and that program producesprinted output, the output should not be directed to the same CMS file that SYSLST isassigned to, since this could cause some messages to be lost. Use one CMS file formessages produced to the SYSLST logical unit, and ASSGN/DLBL to another file for thereport produced by the program.

Unicenter CA-Sort for CMS/DOS will read its control statements from whatever theSYSIPT logical unit has been assigned to, including the virtual reader or a CMS file.When Unicenter CA-Sort has been invoked from another program, the control statementsmust be passed in a parameter list as described in the Unicenter CA-Sort User Guide.


5.6 Applying Maintenance

Although Unicenter CA-Sort program fixes and upgrades will always be provided as anew tape, it might sometimes be necessary to apply a single program fix supplied byComputer Associates.

Follow these steps to apply a fix you have received over the telephone:

1. Create a CMS file that contains the VER and REP statements for the program fix.Call the file

ptfnumber ZAP

where ptfnumber is supplied by your Computer Associates representative.

2. Execute the SRD72PTF EXEC and supply the PTF number as an argument:

SRD72PTF ptfnumber

3. Run the CASRDGEN EXEC to regenerate the CASDSORT DOSLIB.



Chapter 6. Troubleshooting

6.1 Overview

This chapter contains information about:

■ Identifying and resolving problems■ Contacting Computer Associates Technical Support■ Receiving ongoing product releases and maintenance■ Requesting product enhancements

Chapter 6. Troubleshooting 6-1

6.2 Diagnostic Procedures

Refer to the following flowchart for a summary of the procedures you should follow ifyou have a problem with a Computer Associates software product. Each of theseprocedures is detailed on the following pages.



6.2.1 Collecting Diagnostic Data

In the table below, use the left column to categorize the problem your site hasencountered. Then, follow the instructions in the corresponding right column to generateuseful diagnostic data.

For Be Sure to Check

All Problems The rerun job step (to determine if the problem is an isolatedoccurrence). If the rerun is successful, a hardware error may havecaused the problem.

The JCL statements, options and assignments in effect, and theSort/Merge control statements (to determine if there are anyconflicts or problems in coding).

If the job has run successfully before, and if so, when the lastsuccessful run was made. A change may have been made to theoperating system, a master file layout, the data involved, or theinvoking program.

That you have available the following items or information:

■ All JCL used to run the job, including the Sort/Merge controlstatements.

■ All SYSLST output, including messages which may havebeen produced, and a complete partition or supervisor dumpif one was generated.

■ A complete list of all messages produced on the console logfor the failing job step.

All Problems That you have available the following items or information:

■ Knowledge of the release and genlevel being executed. Thismay be obtained from the execution SYSLST output ofCAISERV, which is discussed later under 'CAISERV Utility.'

■ An execution of the failing job step with DIAG specifiedeither on the OPTION control statement or throughSYSPARM. The information produced from the DIAGfunction will often greatly speed the identification andsubsequent resolution of any problem reported. When the jobis rerun, PRINT=ALL and DUMP should also be in effect.

■ If necessary, the input data sets to the failing sort step shouldalso be kept, in order to reproduce the error and test anyproposed fixes.


For Be Sure to Check

Program-InvokedSorts and UserExits

Listings of all user routines being used at program exits (E15,E35, and so forth) and/or the Assembler, COBOL, PL/I or RPGprogram being used to invoke Unicenter CA-Sort. These listingsshould also include link maps.

6.2.1.1 Interpreting Diagnostic Data

When you have collected the specified diagnostic data, write down your answers to thefollowing questions:

1. What was the sequence of events prior to the error condition?

2. What circumstances existed when the problem occurred and what action did youtake?

3. Has this situation occurred before? What was different then?

4. Did the problem occur after a particular PTF was applied or after a new release ofthe software was installed?

5. Have you recently installed a new release of the operating system?

6. Has the hardware configuration (tape drives, disk drives, and so forth) changed?

From your response to these questions and the diagnostic data, try to identify the causeand resolve the problem.


6.2.2 Accessing the Online Client Support Systems

To complement CA Technical Support, Computer Associates provides an online supportsystem, CA-TCC. (CA Total Client Care). This system is provided as a dial-up service toprovide you with total service and support. To enroll in this service, contact your CAClient Service Representative.

6.2.2.1 CA-TCC

CA-TCC is a major extension to existing CA support programs. It provides access to theCA centralized client support database by simply dialing into the CA Technical Supportsystem using CompuServe.

CA-TCC provides online access to PTFs and PIBs for all environments. It includes directproblem reporting, tracking capabilities, and a powerful keyword search facility to allowyou to locate resolutions to problems and download the resolutions for immediateapplication. CA-TCC additionally provides electronic mail (CA-eMAIL+) which allowsyou to contact Computer Associates staff, view product information, and orderdocumentation and other materials online.

To access CA-TCC, you need hardware that can run screen capture software, and thatemulates IBM 3101 or VT-100 terminals. You must also have an asynchronous modem(all baud rates up to 9600 are supported). A CompuServe ID is provided for you whenyou enroll in CA-TCC.

CA-TCC service and features are available 24 hours per day, seven days per week, freeof charge. There is, however, a nominal hourly charge from CompuServe for use of itsnetwork and services.


6.2.3 Calling Technical Support

Computer Associates provides telephone support for all its products.

If you are in North America, refer to the Product Support Directory for the UnicenterCA-Sort Technical Support phone number. Outside North America, call your localComputer Associates Support Center during normal business hours.

Note: Only your local Computer Associates Support Center can provide native languageassistance. Please use English when contacting any North American center.

Emergency phone numbers are also available for after-hours technical support and arelisted on the back of the title page of every CA manual. After hours calls should belimited to severity 1 problems.

If you are unable to locate the technical support number you need, call the number listedon the back of the title page in this manual. The operator will record your call and aCA-product Technical Support representative will call you back.

If you are unable to resolve the problem, please have the following information readybefore contacting Computer Associates Technical Support:

■ All the diagnostic information described in "Collecting Diagnostic Data."

■ Product name, release number, operating system and genlevel.

■ Product name and release number of any other software you suspect is involved.

■ Release level and PUTLEVEL of the operating system.

■ Your name, telephone number and extension (if any).

■ Your company name.

■ Your site ID.

■ A severity code. This is a number (from 1 to 4) that you assign to the problem. Usethe following to determine the severity of the problem:

1 = a "system down" or inoperative condition

2 = a suspected high-impact condition associated with the product

3 = a question concerning product performance or an intermittent low-impactcondition associated with the product

4 = a question concerning general product utilization or implementation


6.2.4 Generating a Problem Report

Once a Computer Associates Technical Support representative has determined that yourproblem requires further investigation, you can use the CAISERV utility to generate aproblem report.

6.2.5 CAISERV Utility

The CAISERV diagnostic facility produces a problem report for you to fill out and sendin with all problem documentation.

CAISERV also produces a short report on the Computer Associates products that youhave installed. You should also send this information to help Technical Support solveyour problem.

You invoke CAISERV, execute the CAISERV proc in your sample JCL library:

// JOB CAISERV

// EXEC CAISERV

/&

Edit the JCL to your installation's standards, and submit the job.

The messages you may encounter when running CAISERV are:

CAPP999E INSUFFICIENT STORAGE TO PROCESS CAISERV.

Reason: Sufficient storage was not allocated to execute CAISERV.

Action: Use at least 100K of storage for executing CAISERV.

*** PRODUCT CAISERV MODULE 'modulename' NOT ACCESSIBLE ***

Reason: Libraries were not properly concatenated.

Action: Review the JCL and reexecute CAISERV.


This job will produce the following problem report to SYSPRINT:

� �CAISERV 1 � � COMPUTER ASSOCIATES PRODUCT STATUS REPORT � �4/13/�1 (MM/DD/YY) 18.21.19 (HH.MM.SS) PAGE 1

��

� �

� COMPUTER ASSOCIATES PROBLEM REPORT SHEET �

� (ALWAYS COMPLETE THIS AND SUBMIT IT AND THE FOLLOWING PAGES WITH ANY PROBLEM) �

� �

��

� �

� COMPANY NAME COMPANY ADDRESS �

� -------------------------------------- ------------------------------- �

� �

� ------------------------------- �

� �

� ------------------------------- �

� CONTACT NAME TELEPHONE NUMBER �

� ------------------------- ------------------------- �

� �

��

� �

� OPERATING SYSTEM PUT LEVEL I/O DEVICES ATTACHED �

� UNDER VSE/ESA 5.2.2 ----------------- ON CPU FF6��43�9�� ---------------------------- �

� �

� ---------------------------- �

� OTHER SYSTEM SOFTWARE �

� (VENDOR AND/OR IBM) ---------------------------------------------------------------------------- �

� �

��

� �

� PROBLEM SEVERITY PROBLEM TYPE �

� (CRITICAL, COSMETIC, ETC) -------------------- (INTERMITTENT, REPRODUCIBLE, ETC) ------------------ �

� �

��

� �

� DESCRIPTION OF PROBLEM �

� �

� �

� �

� �

� �

� �

��

�

Fill in the form completely. This information will be logged into the Computer AssociatesTechnical Support system and will be tracked from the time it is reported to the time it isresolved.


On the next page of the problem report, describe the problem you are experiencing. Theheadings on this page look like this:

� � COMPUTER ASSOCIATES PROGRAM STATUS REPORT CAISERV-�1 PAGE �2

��

� �

� COMPUTER ASSOCIATES PROBLEM REPORT FORM �

� �

��

� �

� PROBLEM DESCRIPTION : �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

� �

��

�


The last page of the problem report provides a status of the Computer Associatesproducts that you have installed. In most instances, this report includes the productrelease number, genlevel, and installation options. This is a sample Unicenter CA-Sortreport:

� �CAISERV 1 � � COMPUTER ASSOCIATES PRODUCT STATUS REPORT � �5/13/97 (MM/DD/YY) 11.28.39 (HH.MM.SS) PAGE 15

CASD7��I CA-SORT DOS VERSION 9.� GENERATION OPTIONS IN EFFECT

CASD7�1I GENLVL= �2�4SD9��

CASD7�2I PACKAGE PREFIX= CA9�

CASD7�3I SYSTEM INSTR SET= 37�/43��

CASD7�4I MODEL CLASS= 4341

CASD7�5I OPSYS= DOS/VS(E)

CASD7�6I MSG= BOTH

CASD7�7I PFIX= NO

CASD7�8I OPT= E

CASD7�9I DYNAM/D= YES CURRENT LEVEL RUNNING= 6.�

CASD71�I STORAGE= 4��K

CASD723I RESERVED= �128K

CASD711I DEFDTF= CANCEL

CASD715I PREOPEN= NO

CASD716I DISK= 335�, 3375, 338�, 339�, FBA

CASD718I EQUALS= YES

CASD719I DYNAMFI= YES CURRENT LEVEL RUNNING= 6.�

CASD72�I CHECK= YES

CASD721I WKASN= ON

CASD731I WKXTNTS=�25

CASD722I DYNALOC= NO

CASD724I RC AT EOJ= YES

CASD725I JCLPRNT= ALL

CASD726I INVPRNT= ALL

CASD727I INVCNCL= NO

CASD728I SPECIAL= (11,13)

CASD729I CHALT= NO

CASD73�I ALTSEQ= NONE

CASD732I CENTURY WINDOW= 1917-2�16| CASD733I DSPSIZE= 1�24

�

6.2.5.1 CA90DEVC Utility

The CA90DEVC diagnostic facility produces a device characteristics report for aproblematic device. To invoke CA90DEVC, use the following JCL:

// ASSGN SYS��,device

// EXEC CA9�DEVC


6.3 Product Releases and Maintenance

New users of Unicenter CA-Sort are provided with a distribution tape containing thecurrent version of the system. Clients are requested to operate only under currentlysupported releases of Unicenter CA-Sort

Standard user documentation is also provided to Unicenter CA-Sort users. Updates tothis documentation are provided automatically to all clients having current maintenanceagreements.

Clients with current maintenance agreements also receive ongoing Unicenter CA-Sortmaintenance. When a new release of the system is available, a notice is sent to allcurrent Unicenter CA-Sort clients.

6.4 Requesting Enhancements

Computer Associates welcomes your suggestions for product enhancements. Allsuggestions are considered and acknowledged. You can use either of two methods torequest enhancements:

■ Contact your Account Manager who will initiate a Demand Analysis Request (DAR)for you.

■ Complete the Demand Analysis Request form located at the end of this guide andreturn it to Computer Associates.

The DAR system serves as a central receiving point for all enhancement requests.


Index

Special Characters$FIINTR1 module 2-5

AALTSEQ, installation parameter 2-12ANALYZE control statement 4-1APAR 6-5ASSGN statement 5-1, 5-4

BBIAS factor 4-3Block size 4-5Buffers 4-7

CCA-TCC (online support system) 6-6CA72A000 5-2CA90PSTA utility program 4-9CAISERV 2-2, 6-8Calculation

of disk work space 4-1of minimum main storage 4-5

CANCEL 2-6CASDOS EXEC 5-6CASDSORT 5-2, 5-7CASORT macro

assembly 2-1generation example 2-16storage limit 4-8

CASRDGEN 5-2, 5-7CCW 4-5CHALT, installation parameter 2-13CHECK, installation parameter 2-7CHKPT|CKPT 5-5CISIZE 2-3CMS exec 5-1CMS FETCH command 5-6CMS/DOS 5-1, 5-4Computer model codes 2-15

DDataspace support, CA90PSTA utility program 4-9DEFDTF, installation parameter 2-6DIAG option 6-5Disk space management systems 2-3DISK, installation parameter 2-7DLBL/LABELDEF 5-4DOS SAM 5-4DOS/MVT 2-4DOSLIB 5-2DSPIZE, installation parameter 2-14DTF determination 2-3, 2-6DTFSD 5-4DYNALOC, installation parameter 2-9DYNAMD, installation parameter 2-5DYNAMFI, installation parameter 2-5

EEQUALS, installation parameter 2-6, 4-5EXCP 4-7EXEC 5-1Exit E15 6-4Exit E35 2-7, 6-4

FFETCH 5-6File size estimation 4-1

GGeneral register contents 3-3

IIDAL 4-5IJSYSLS 5-6In-core sort 1-1, 4-3Initiation 1-1INPFIL 5-4, 5-5INREC 4-5Installation Options 5-2Interface

SORTPARM 3-1Unicenter CA-Dynam/D 2-5, 2-9

Index X-1

Interface (continued)Unicenter CA-Dynam/FI 2-5

INVCNCL, installation parameter 2-9Invoked operation 1-1INVPRNT, installation parameter 2-3ISAM 5-5

JJCLPRNT, installation parameter 2-3

LLabels, use in DTF determination 2-6LIOCS modules 3-3LST 2-2

MMain storage 2-4, 4-5Merge order 1-2Message routing 2-2Mixed DASD support 2-7Modal record length 4-4Model Codes 2-15MODEL, installation parameter 2-2MODS control statement 4-5MSG, installation parameter 2-2

OOnline support systems 6-6OPSYS, installation parameter 2-4OPT, installation parameter 2-2, 4-2Optimim Main Storage 4-7Optimization 4-1, 4-2, 4-4OPTION 2-4, 4-8OUTFIL 5-4

PPage fixing 2-3, 3-1Paging 4-8Performance 2-9, 4-1, 4-7PFIX, installation parameter 2-3, 5-4, 5-7PHASE, installation parameter 2-2PREOPEN, installation parameter 2-3PRF 6-7PRINT 6-4Private CCW Translation 2-3

ProductSupport Directory 6-6

Program fix 5-7PTF 6-5PUTLEVEL 6-6

RRC, installation parameter 2-11RDW 5-4RECORD control statement 4-4Record counts 2-7RESERVE, installation parameter 2-5RETURN 3-3Return address 3-3

SSAVE 3-3Save area 3-3SIZE keyword 4-1, 4-8SORTPARM exit 3-1, 4-8SPECIAL, installation parameter 2-11SRD72PTF 5-7SRTCHECK 5-3STORAGE

installation parameter 2-4OPTION satement keyword 4-8OPTION statement keyword 2-4

Storage requirementsminimum 4-5optimum 4-7

Support, online systems 6-6SVA 4-5, 4-7SYSIPT 5-6SYSLST 5-6SYSPARM 6-5

UUnicenter CA-Dynam/D interface 2-5, 2-9Unicenter CA-Dynam/FI interface 2-5

VVSE support 1-1, 2-4

WWKASN, installation parameter 2-9

X-2 Unicenter CA-Sort Systems Programmer Guide

WKXTNTS, installation parameter 2-11WORK 5-5Work file

device types 4-5dynamic allocation 2-9logical units 2-9use of the DISK installation parameter 2-7use of the WKASN installation parameter 2-9

YY2PAST, installation parameter 2-14

Index X-3

Documents

Unicenter CA-Sort for VSE · and optimizes virtual storage management. ... CA-Sort in any programming language. ... (phases). Each part is loaded from the