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-1 1.1 Overview ...... 1-1 1.2 Phases ...... 1-2
Chapter 2. Installation Options ...... 2-1 2.1 The CASORT Option Macro ...... 2-1
Chapter 3. SORTPARM - Overriding Unicenter CA-Sort Parameters ..... 3-1 3.1 Overview ...... 3-1 3.2 Method of Operation ...... 3-2 3.3 User Considerations ...... 3-3 3.4 Examples ...... 3-4
Chapter 4. Performance Considerations ...... 4-1 4.1 Optimization Aids ...... 4-1 4.2 Main Storage Calculations ...... 4-5 4.3 Unicenter CA-Sort Dataspace Support and the CA90PSTA Utility Program .. 4-9
Chapter 5. Running Unicenter CA-Sort Under CMS/DOS ...... 5-1 5.1 Overview ...... 5-1 5.2 Modifying Installation Options (CASORT Macro) ...... 5-2 5.3 Displaying Unicenter CA-Sort Product Options (SRTCHECK Program) .... 5-3 5.4 Using Unicenter CA-Sort Under CMS/DOS ...... 5-4 5.5 Executing Unicenter CA-Sort for CMS/DOS ...... 5-6 5.6 Applying Maintenance ...... 5-7
Chapter 6. Troubleshooting ...... 6-1 6.1 Overview ...... 6-1 6.2 Diagnostic Procedures ...... 6-2 6.3 Product Releases and Maintenance ...... 6-12 6.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 Unicenter CA-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 modifying them using the CASORT option macro. 3 Describes user exits, which allow you to modify the supplied code to meet your data center's standards. 4 Covers performance considerations, optimization aids and main storage allocation. 5 Explains how to use Unicenter CA-Sort in a CMS/DOS environment. 6 Provides debugging methods and lists the information needed by Computer 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 elect to use data spaces instead of work files. This feature can be implemented using the new DSPSIZE parameter available on the CASORT macro and on the Unicenter CA-Sort OPTION 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:
Name Contents Unicenter CA-Sort Installation Guide Installation procedure to install Unicenter CA-Sort Unicenter CA-Sort User Guide Complete information on all of Unicenter CA-Sort available to the general user, and command syntax. Unicenter CA-Sort/Unicenter CA-SRAM Error messages and return codes. For Message Guide each message an appropriate reason and possible actions are listed. Unicenter CA-SRAM User Guide Complete information on all of Unicenter CA-SRAM available to the general user, including command syntax. Unicenter CA-SRAM Installation Guide Installation procedure to install Unicenter CA-SRAM. Unicenter CA-SRAM Systems Planning, installation, and maintenance Programmer Guide procedures.
All guides are updated as required. Instructions accompany each update package. Technical changes are identified by a revision bar (|) in the left margin. Revision bars are not used for editorial changes and new manuals.
About This Guide vii
Related Publications
The following publications relate to Unicenter CA-Sort and are available from Computer Associates: ■ CA-CIS documentation set The following publications are not produced by Computer Associates but are referenced in 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:
UPPERCASE Identifies commands, keywords, keyword values and operators which must be coded exactly as shown. MIXed Cases Identifies command abbreviations. The uppercase letters are the minimum abbreviation; lowercase letters are optional. Delimiters , ( ) = and blanks
The following clarify command syntax; do not type these as they appear:
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 than once.
Sample Command Explanation SORT SORT is operator keyword. [WORK={n|DA}] 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 partition and optimizes virtual storage management.
Initiation of Unicenter CA-Sort is under the user's control; execution may be started either by the EXEC job control statement in the application JCL, or by invoking Unicenter CA-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 the core image library and adapted internally according to the sort/merge techniques defined by the user.
Phase 0 (Initialization and Optimization Phase)
Phase 0 will be executed in every SORT and MERGE execution. During this phase, the JCL 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 messages will be printed on the printer and console if detected. In addition, the sorting environment is checked carefully and, internally, execution variables and capacity estimates are made based upon the CPU, storage available, disk devices on the system, and other similar factors. In general, Unicenter CA-Sort optimizes itself to run most efficiently using information 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 are opened 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 in sequence. Whenever possible, Unicenter CA-Sort attempts to keep these strings entirely in 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 is then opened and the sorted sequences written to it. The creation of sorted strings from the input 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 created in Phase 1 is greater than the 'merge order.' Merge order is the maximum number of strings 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 the total number of strings. Phase 2 will end when the number of strings remaining is less than 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 file is opened and the strings in memory or from the work files are combined in sequence to form 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 must be 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 is chosen, it must be renamed to be SORT before testing with COBOL programs which invoke 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 root phase. If the name SORT is not chosen, the root should be renamed to SORT manually. Default = CA90SORT Note: Either the default phase name or the name SORT must be used for the Unicenter CA-Sort root phase when executing CAISERV. MODEL= Indicates the computer model on which Unicenter CA-Sort is installed. Use the table on page 2-16 to select the proper model code. Unicenter CA-Sort uses this value to determine the instruction set to be used, and to obtain CPU timing estimates for optimization 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. If work files must be opened, each extent for SORTWKn is opened sequentially as the previous one is filled. The remaining work files and extents are opened only as needed. This is the preferred reply for multiprogramming or teleprocessing installations. D The sort is to be optimized on CPU time, and open all extents on all work files if any work space is needed to spread I/O across volumes. This should be used only for small installations. Default = E
2-2 Unicenter CA-Sort Systems Programmer Guide
Keyword Description MSG= Indicates how runtime messages for JCL-initiated sorts (by the EXEC statement) are to be routed. The default may be overridden using the ROUTE= keyword on the OPTION control statement. LST Runtime messages CASD201I-CASD599I will be routed to the printer whenever SYSLST has been assigned. LOG Non-Phase 0 messages are to be routed to the operator's console (SYSLOG). BOTH Runtime messages CASD201I-CASD599I will be printed on 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 is LST because this response improves the performance of small sort/merge tasks. ■ Runtime messages for program-invoked sorts are NOT affected by this parameter, and will be routed to SYSLOG regardless of the above response. ■ Phase 0 messages are NOT affected by this parameter and will be directed to SYSLST regardless of the parameter specified. ■ If MSG=LOG or BOTH is specified, runtime messages will only be directed to the console at end-of-job or if a fatal execution error occurs. JCLPRNT= Indicates which messages are to be printed for JCL initiated sorts (by the EXEC statement). ALL All messages. NONE No messages. CRITICAL Only E level messages. Default = ALL
Chapter 2. Installation Options 2-3
Keyword Description INVPRNT= Indicates which messages are to be printed for program invoked sorts. ALL All messages. NONE No messages. CRITICAL Only E level messages. Default = CRITICAL PREOPEN= Indicates whether disk input files are to be opened in Phase 0 to obtain the CISIZE for FBA files from the VTOC or check for a change of device type between CKD and FBA. YES This response should be coded if FBA disk devices are in use on the system, even if not used for sort files. NO A mixture of CKD and FBA or all FBA devices does not exist in the installation. Disk input files will not be opened in Phase 0 to check for a change in disk device type. Default = NO Users without a disk space management product must have all logical units assigned before OPEN (except for VSAM/SAM input and output files). Note that specifying of PREOPEN=YES, although acceptable, may introduce a small amount of unnecessary overhead. Any user with FBA devices should specify YES to ensure that Unicenter CA-Sort can obtain the CISIZE necessary to deblock the input file or react dynamically to a change in device type between CKD and FBA devices. PFIX= Indicates whether virtual pages are to be fixed in storage for better performance as follows: YES Unicenter CA-Sort should attempt to page fix control blocks and buffers up to the limit specified in the supervisor ALLOCR operand for each partition. A minimum of 6-8K real storage will be page fixed during execution. NO No page fixing or private CCW translation is to be done. Default = YES YES is recommended on VSE to allow control blocks and I/O buffers to be fixed and Private CCW Translation to occur for input, output and work files. This will reduce supervisor overhead and paging. PFIX=YES is not allowed for non-VS systems.
2-4 Unicenter CA-Sort Systems Programmer Guide
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-Sort requires that the MVT parameter be coded when running an MVT/VSE. Default = VSE STORAGE= Optional operand used to set a maximum limit on the use of main storage. The format is nnnnK. Unicenter CA-Sort will not exceed the value specified in this parameter unless overridden using the STORAGE keyword on the OPTION control statement. A reasonable limit is usually in the range 256K-512K. Default = No limit When determining the amount of main storage to use, Unicenter CA-Sort will first override the value specified in this operand with a value from the STORAGE= keyword on the OPTION control statement, if present. The result is then compared against the partition size and the SIZE= parameter on the EXEC statement (or space remaining in the partition, if invoked). The smallest of these three values is then set as the maximum storage limit for the run. RESERVE= Optional operand specifying the minimal amount of partition storage to be reserved as a GETVIS area and not to be used by sort. The format is nnnnK. Default = 128K
Chapter 2. Installation Options 2-5
Keyword Description DYNAMD= Indicates whether Unicenter CA-Sort is to interface to Unicenter CA-Dynam/D, as follows: YES Unicenter CA-Dynam/D is installed and active. See 'Unicenter CA-Sort and Unicenter CA-Dynam/D Interface' in the Unicenter CA-Sort User Guide for the facilities provided by the Unicenter CA-Dynam/D interface. NO Unicenter CA-Dynam/D is not installed and/or activated. Default = NO If the interface has been enabled, either at generation time using this parameter, or at execution time with the OPTION control statement, Unicenter CA-Dynam/D must be active on the system. Failure to have Unicenter CA-Dynam/D active will cause every sort to cancel with the IBM message '4n80I INVALID FILE TYPE'. DYNAMFI= Indicates whether Unicenter CA-Sort is to interface to Unicenter CA-Dynam/FI, as follows: NO Unicenter CA-Dynam/FI is not installed and activated on the system. YES Unicenter CA-Dynam/FI is installed and active. See 'Unicenter CA-Sort and Unicenter CA-Dynam/FI Interface' in the Unicenter CA-Sort User Guide for the facilities provided by the Unicenter CA-Dynam/FI. Default = NO
2-6 Unicenter CA-Sort Systems Programmer Guide
Keyword Description DEFDTF= Indicates the default DTF type to be built for the SORTINn and SORTOUT files if Unicenter CA-Sort cannot determine the proper type from labels or from existing assignments, as follows: TAPE A tape DTF will be built if the logical unit has not been assigned correctly and labels were not submitted. DISK A sequential CKD disk DTF will be built if the proper determination cannot be made. FBA Same as DISK, but an FBA DTF will be built. CANCEL The default indicates the sort/merge is to terminate if the proper labels and/or assignments are not present. Default = CANCEL The DEFDTF value will only be used as a last resort to determine the type of DTF to be built for input and output files. Typically, DTF determination will be made by the TLBL/DLBL statement found in the job stream, with the logical unit assignment and DEFDTF values immaterial. Only if the logical unit is unassigned and a DLBL/TLBL was not found will the DEFDTF value take effect. 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 the same sequence as they were read. Default = NO
Chapter 2. Installation Options 2-7
Keyword Description CHECK= Indicates whether record counts should be checked at the end of Phase 3 when an E35 exit is in use. YES Record counts should be checked. If found to be unequal the message CASD207W will be issued. This is compatible with prior versions of Unicenter CA-Sort. NO Unequal record counts will be accepted without error. Default = YES This parameter, which may be overridden using the OPTION statement, may be used to prevent abends caused by COBOL programs which do not properly process all records in the Output Procedure that were sorted in Phase 1. A 'Record Count Off' situation will be ignored only if CHECK=N is in effect and an E35 exit has been specified (COBOL sorts always use an E35 exit). CHECK=Y is the recommended default to ensure output integrity.
2-8 Unicenter CA-Sort Systems Programmer Guide
Keyword Description DISK= Indicates the DASD devices which may be used for sort work allocations. Unicenter CA-Sort uses the values specified in this operand to optimize the sort work block size chosen. Specify one or more disk devices, in any combination, that Unicenter CA-Sort should consider when performing Phase 0 calculations for work block size. Do not specify devices which are never used for sort work files. The allowable choices are 2311, 2314, 3330, 3330-11, 3340, 3350, 3375, 3380, 3310, 3370, 3390 and 9345. For FBA disk devices 93xx, specify 3370. Default = None. Must be specified. Specifying devices in this fashion means that users with a disk space management product need not have the SORTWKn logical units preassigned to the proper devices, and the block size chosen by Unicenter CA-Sort will be of a size that will fit on any device specified in this parameter, thus allowing pooling of various DASD types. Because the work block size is based upon values in this table and not the supervisor PUB table, a larger work block size will probably be chosen, resulting in fewer I/Os to the work files if the smaller capacity devices are not used for work files. This parameter has no effect on SORTIN or SORTOUT device types, and is only used for work file block size calculations. There are no checks made within Unicenter CA-Sort to ensure that a work file has been allocated on one of the devices specified in this table. Note: It is the user's responsibility to specify the allowable DASD types to ensure peak track utilization and performance, and to avoid I/O errors caused by writing a large block on a small-capacity device not specified in the table.
Chapter 2. Installation Options 2-9
Keyword Description WKASN= Indicates whether Unicenter CA-Sort is to use the devices specified in the DISK= parameter or the DASD devices which are assigned to work file logical units when determining the optimum value for work file block size. The allowable choices are: OFF Use the disk devices which have been specified in the DISK= parameter. ON Use only the devices which are assigned to work file logical units. Default = OFF Unicenter CA-Sort is able to operate more efficiently when the type of DASD devices which will actually be used for work file allocations can be determined during Phase 0. If a disk space management product is in use, especially in a mixed DASD environment, the work file logical units may not be reliably assigned at execution time. In this case, WKASN=OFF should be specified to allow block size calculations to be based on all devices which may be used for work file allocations. If the DISK= parameter has been specified correctly, all sorts will run, regardless of the devices used, but degraded performance may result if all specified devices are not used for work file allocations. If correct assignments are normally provided for the work file logical units, as is the case when running the IBM sort/merge product, specifying WKASN=ON may provide better performance by eliminating unused devices from the DISK= parameter and allowing a more optimum work file block size to be calculated. Only the DASD devices which are assigned to work file logical units will be used in block size calculations. WKASN=ON may be used with a disk space manager only if the work file allocations are made on one of the device types assigned. The WKASN default setting may be overridden using the OPTION control statement. As is the case with the DISK= installation parameter, only work file block size calculations are affected by the setting of the WKASN value. INVCNCL= For program invoked sorts, indicates whether to pass a return code or cancel the job when an error is encountered. NO Transfer control to the calling program with a return code. YES Cancel the job. Default = NO
2-10 Unicenter CA-Sort Systems Programmer Guide
Keyword Description DYNALOC= Indicates whether work files will be allocated dynamically by Unicenter CA-Sort when no SORTWKn labels are defined for a Unicenter CA-Sort execution. NO All work files are to be provided by the user. vvvvvv,n Work files will be allocated dynamically during Unicenter CA-Sort execution. DYNAMD=Y must be specified and Unicenter CA-Dynam/D Release 5.3 or above must be installed and active. vvvvvv is required and may be 1-6 alphanumeric characters, indicating where work file space will be allocated. It may be any valid DASD serial number, a Unicenter CA-Dynam/D generic volume serial number or disk pool-ID. n is optional. If specified, it must be in the range 1-9, indicating the number of work files to allocate. If omitted 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 conditional JCL. 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 allocated for SORT work files. Any value from 1 to 255 is valid. Default = 25
Chapter 2. Installation Options 2-11
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 extra blank statement). 4. Ignore STORAGE= from the OPTION control statement for program invoked sorts. 5. Ignore STORAGE= from the OPTION control statement for JCL initiated sorts. 6. A default of FILES=1 for merge. 7. Optimize VSAM buffer space for files accessed by the option FILNM parameter for improved performance. Requires the default reserve value to be increased by 55K for each simultaneously 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 to avoid 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 VSAM maximum record length for VSAM/SAM undefined files. 15. Process invoked SORT runtime messages CASD201I and above according to the MESSAGE= parameter of the Unicenter CA-Sort macro. 16. Always flag a long tape block as an error (message CASD203E). Exit E18, exit E38, or bypass options may be used. 17. Version 1 tape DTF support for EPAT.
2-12 Unicenter CA-Sort Systems Programmer Guide
Keyword Description ALTSEQ= Indicates a default alteration of the collating sequence for AQ format control fields. Every sequence definition must consist of four hexadecimal digits in the range of 0-9 or A-F. ff represents the character whose position in the collating sequence is to be changed. tt represents the new position in the collating sequence the character is to occupy. Default = No alternate sequence. The EBCDIC collating sequence is in effect. The moved character (ff) is considered equal to the character already occupying the position to which the character is being moved (tt). The character in the tt position is not considered to be moved, however, and it may have its sequence altered as an ff argument, if desired. Control fields which have been defined using the AQ format code are affected by the new collating sequence. If CHALT is in effect (see the CHALT generation parameter below or the CHALT keyword in the OPTION control statement), control fields with the CH format code are also affected by the new sequence. If ALTSEQ is not specified, all AQ control fields collate according to the standard EBCDIC sequence. An ALTSEQ control statement may override any or all of the alterations specified in the CASORT generation macro ALTSEQ parameter. CHALT= Indicates whether CH format control fields are affected by an alternate collating sequence as in the case of AQ format control fields. The CHALT generation parameter can be overridden by the CHALT or NOCHALT keywords in the OPTION control statement. YES CH control fields collated by an alternate sequence. NO CH control fields collated by the standard EBCDIC sequence. Default = NO
Chapter 2. Installation Options 2-13
Keyword Description Y2PAST= Specifies the type of century window (fixed or sliding) to be used when interpreting 2-digit years. A century window spans a 100 year period, such as 1950 to 2049, and determines how 2-digit years are handled. If the century window is set at 1950 to 2049, then a value of 60 would be interpreted as 1960. If the century window is set at 1970 to 2069, a value of 60 would be interpreted as 2060. F Specifies a fixed date at which the century window is to begin. F can be any value between 1000 and 3000. If, for instance, Y2PAST=1997, then the century window would begin in 1997 and span from 1997 to 2096. S Specifies the number of years before the current year that the century window is to begin. S can be any value between 0 and 100. The default is 80. If, for example, the current year is 1997, by default, the century window would begin at 1997 - 80 or 1917. When the current year becomes 1998, the beginning of the century window will change to 1998 - 80 or 1918. In this case, the century window is now 1918 to 2017. | 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.
2-14 Unicenter CA-Sort Systems Programmer Guide
Computer Model Codes
Machine Model Code Configuration 360/22 25 All configurations 360/25 360/30 30 All configurations 360/40 40 All configurations 360/50 50 All configurations 360/65 65 All configurations 370/115 115 All configurations 370/125 125 All configurations 370/135 135 All configurations 370/138 138 All configurations 370/145 145 All configurations 370/148 148 All configurations 370/155 155 With DAT feature 370/155 155 Without DAT feature 370/158 158 All configurations 370/168 168 All configurations 3031 3031 All configurations 3032 3032 All configurations 3033 3033 All configurations 3080 3080 All configurations 3090 3090 All configurations other 30xx 3031 All configurations ES9000 9000 All configurations 4321 4331 All configurations 4331 4331 All configurations 4341 4341 All configurations 4361 4361 All configurations 4381 4381 All configurations 9370 9370 All configurations
Chapter 2. Installation Options 2-15
2.1.2 Sample Option Generation
The following example shows how typical generation options would be specified in the CASORT macro to generate a root phase for an installation running under VSE Release 2 on a 4341 with a mixture of 3330, 3350 and FBA disks. Although the installation simulates 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=3K, .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=124 .DATA SPACE USAGE IS SET ᑍ END /ᑍ // EXEC LNKEDT /&
2-16 Unicenter CA-Sort Systems Programmer Guide
Chapter 3. SORTPARM - Overriding Unicenter CA-Sort Parameters
3.1 Overview
Due to the increasing complexity of job mixes found in today's data centers, it would often be desirable to be able to override particular sort/merge parameters based upon specific sets of criteria, such as time-of-day, paging rate, teleprocessing activity, and so forth. In the past, the only methods available were to use different sets of sort JCL based on 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 program and respecify a number of crucial parameters used by Unicenter CA-Sort so that it can be tailored to meet each installation's specific needs. For example, SORTPARM could be used 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 changing the sort control statements for each run. ■ Change the amount of storage the sort/merge is to use, based upon the shift, day of the week, number of active partitions, paging rate, CICS up, and so forth. ■ Change the message routing options from their generated defaults, or to correct certain options given on outmoded JCL or invoked sorts. ■ Change the internal optimization schemes and work file usage patterns for certain critical job streams or month-end processing. ■ Allow or disallow page fixing, based upon system load and amount of pages in the page pool. These are only examples of the types of flexibility the SORTPARM exit provides. The user may update the various options based upon any criteria that will make the installation 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 an invoked program have been processed during Phase 0, a user program with the default phase name 'SORTPARM' is loaded into the partition and given control. User routines with other phase names to perform different processing will be called by Unicenter CA-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 by general register 1. The values in the list represent the parameters currently in effect, set either at generation time or by the control statements processed. These values may be modified as needed, based upon any user criteria desired.
When control is given back to Unicenter CA-Sort, the control blocks within Unicenter CA-Sort will be updated to reflect any changes made, and Phase 0 processing will continue, using the new values. Parameters not modified by the user will retain the same values as presented to the routine.
To cause the user program to be loaded and executed, either form of the following parameter 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 no name is specified, the default phase SORTPARM will be loaded. Although only one user routine will be loaded by Unicenter CA-Sort per sort/merge execution, the ability to specify a phase name allows multiple routines to be coded and executed based upon the type 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-2 Unicenter CA-Sort Systems Programmer Guide
3.3 User Considerations
Upon entry, general registers 1, 13, 14 and 15 will be set by Unicenter CA-Sort according to VSE linkage conventions to contain the address pointers below. All registers should be saved upon entry to SORTPARM and restored before exiting using the SAVE and RETURN macros.
Register Contents 1 Address of the parameter list. 13 A save area in which to save, upon entry, the registers used by Unicenter CA-Sort. 14 Return address within Unicenter CA-Sort. 15 Entry point of the 'SORTPARM' user routine.
If any subroutines or LIOCS modules are used in the user routine, it is the user's responsibility to provide a separate register save area within SORTPARM, save register 13 upon entry, and load the address of the new save area into register 13. Before exiting and restoring the registers used by Unicenter CA-Sort, register 13 must be reloaded with the saved value.
The SORTPARM exit must not be linked as nonrelocatable. Self-relocating or relocatable exits may be used (S,*, or +0 on the PHASE statement). The use of the SORTPARM exit does not affect the operation of any other exits being used.
Sufficient storage must be available in the partition in excess of the 30K minimum storage requirement of Unicenter CA-Sort, in order to load the user routine. An 'OP77I CANCELLED DUE TO INVALID ADDRESS' will result if there is not.
The SORTPARM exit will be activated after the control statements (or parameter list for invoked sorts) have been processed and, therefore, any value reset through the use of this exit routine will override any options specified on control statements.
Chapter 3. SORTPARM - Overriding Unicenter CA-Sort Parameters 3-3
3.4 Examples
3.4.1.1 Example 1
Assembler language DSECT showing the parameters passed to a user SORTPARM routine for modification. The number to the left of each entry is the displacement in hexadecimal from the beginning of the parameter table for each value which may be modified. 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 Unicenter CA-Sort Systems Programmer Guide
3.4.1.2 Example 2
COBOL linkage section showing the parameters passed to a user SORTPARM routine for modification. 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.
Chapter 3. SORTPARM - Overriding Unicenter CA-Sort Parameters 3-5
3.4.1.3 Example 3
Sample SORTPARM exit to set the storage used to 100K from 6:00 AM to 6:00 PM, and reset 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,C15K .USE STORAGE=15K AT NIGHT ST 3,(,2) .STORE IN STORAGE SLOT IN PLIST B RETRN .RETURN TO Unicenter CA-Sort DAYTIME EQU ᑍ L 3,C1K .ELSE USE 1K 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) C1K DC F'124' .CONSTANT 1K FOR DAY USE C15K DC F'1536' .CONSTANT 15K FOR NIGHT USE LTORG END SORTPARM
3-6 Unicenter CA-Sort Systems Programmer Guide
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. It only needs a work space size (expressed in tracks) corresponding to the sort input file volume (plus a reserve of some 10percent). Typically, the IBM sort systems require an increase of between 25 percent and 100 percent. The amount of Unicenter CA-Sort disk work space may be considerably reduced to achieve the same (or comparable) maximum sort capacity possible with the IBM sort. The space which becomes free may be assigned to other programs. The necessary amount of work space tracks for Unicenter CA-Sort should be determined by using the ANALYZE statement which gives worst-case space estimation (for example, with enough reserves for a different distribution of records). The amount calculated may be used for subsequent sort executions only if the following 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 on the total sort performance. It should show, whenever possible, the expected number of input records or, at least, the maximum number of records which may be processed. The estimated value should never be lower than the actual file size. In order to achieve comparable working environments, the work space definition should be 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 be customized 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 the above two options, priority may be given to one factor. OPT=D ("dedicated") optimizes elapsed and CPU time when the sort time itself is a critical factor (for example, large sorts which occupy the whole machine) or when the CPU utilization is to be reduced. This option is to be preferred when system timing and/or comparison measurements are to be performed. OPT=E ("EXCP") optimizes the number of I/O accesses and should be used when the total multiprogramming throughput is to be increased, or for systems with heavy teleprocessing 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 is shown on the first line printed by Unicenter CA-Sort: CASDI SORT FIELDS=(.... ᑍyymmSD,Eᑍ ↑↑ installed genlevel ------+ | | optimization default=E ------+ The success of the different optimization schemes is dependent on meaningful file estimation (SIZE= parameter on the SORT control statement).
4-2 Unicenter CA-Sort Systems Programmer Guide
■ BIAS factor The BIAS value is a measure of string length to work space usage and indicates the availability of preordered sequences in the sort input file. Its range is between: 100 - file ordered in reverse sequence 150 - 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 (for example, being more than 300-400) it may be specified for the subsequent sort run on 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 for critical 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 an in-core sort was performed, BIAS=NA will be printed, indicating the bias value was "not available."
Chapter 4. Performance Considerations 4-3
■ Optimization for variable-length record sorts The performance of sorting applications using variable-length records is dependent upon the correct specification of the modal record length. The modal record length describes the length of the most frequent record in the file. It may also be approximated by the average record length. The average record length is automatically calculated by Unicenter CA-Sort and printed. For subsequent runs this value may be defined as the l5 parameter on the RECORD statement. Considerable time savings will result from a correct l5 specification. Example of optimization: Run Number 1 // JOB...... : : // EXEC SORT CASDI SORT FIELDS=(...... CASDI RECORD TYPE=V,LENGTH=2 : : CASD32I L5=1 assumed l5 default
CASD21I END SORT PH, BIAS=18 CASD214I AVERAGE RL=12 actual value (large difference | against the assumed l5) | | Run Nbr 2 | // JOB...... +------+ :| :| // EXEC SORT | CASDI SORT FIELDS=(.... ↓ CASDI RECORD TYPE=V,LENGTH=(2,,,,12) : : :
4-4 Unicenter CA-Sort Systems Programmer Guide
4.2 Main Storage Calculations
Allocation of main storage to the sort/merge execution can be the most important factor influencing execution and performance. As more storage is allocated, performance generally improves.
Minimum main storage factors are presented first, followed by some general guidelines for specifying optimum storage values.
4.2.1 Minimum Main Storage
The minimum main storage required by Unicenter CA-Sort is 30K bytes. However, for a given 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 always required. The storage size estimate is 8K if the Unicenter CA-Sort runtime phases are installed in the SVA. If phases are not in the SVA, an additional 10K should be added. ■ Main storage for execution-time generated routines to handle control field extraction, comparison, record selection, reformatting, and so forth. The storage required depends on the number and format of the control fields and the logical relations specified in the SORT/MERGE, INCLUDE/OMIT, SUM, INREC, and OUTREC control statements. In general, these routines will not exceed 4K. ■ Main storage for input/output file DTF (100 bytes) and at least one input/output buffer. The size estimate for the buffer is the larger of either the maximum input or output block size, plus 8 bytes. For FBA input and output files, the file CISIZE instead of BLKSIZE should be used in calculating the buffer size. For VS files, SUM, INREC, and OUTREC processings, an additional record assembly area of maximum logical record length is required for each of the facilities specified. ■ Main storage for user-written exit routines. This is the largest of PH1, PH2, or PH3 exit phase length, unless the phases are preloaded. The amount of storage reserved by Unicenter CA-Sort for each PHn exit will be the larger of the value specified in the length parameter of the MODS control statement, or as determined from the core image library directory entry for the phase length. For further description of the storage management techniques used by Unicenter CA-Sort, refer to the MODS control statement in the Unicenter CA-Sort User Guide.
Chapter 4. Performance Considerations 4-5
■ Main storage used for sorting. There must be enough storage to hold at least four internal records plus two sort work buffers. Internal record length is usually equal to the input record length, E15-modified input record length, or the record length after INREC processing, plus 4 rounded up to a multiple of fullwords. An additional 4 bytes is required for each record when the EQUALS option is in effect. The sort work buffer size used should be the larger of the internal record length plus 16 bytes or the minimum block size for the work file device type. The minimum block sizes for work file device types is as follows:
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
The result of the total main storage size should be rounded up to the next multiple of 4K (for example, 66K yields 68K). This will allow for the additional overhead in page-boundary alignment, CCWs, IDALs, and so forth.
4-6 Unicenter CA-Sort Systems Programmer Guide
4.2.2 Optimum Main Storage
The minimum storage value allows for the Unicenter CA-Sort modules and a minimum number of buffers to be allocated for most record and block sizes. This minimum value is, of course, not the optimum storage value. When storage size is restricted, sort/merge performance decreases due to increased I/O activity. Increasing storage allocations above the minimum will tend to increase the sort work block size, thereby decreasing the amount of I/O performed. Increasing storage is recommended for every sort/merge execution to maximize performance. Most sort/merge executions may be performed efficiently when 150K-250K of storage is available to the package.
The following figure illustrates how adding main storage can affect performance in a positive 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=4K | | | 1 I/O Buffers | || || || || || +------+ Storage=8K Although the above example is only for illustrative purposes, it is evident that increasing the main storage available provides the most benefit in the area of I/O buffers. In the example, by doubling the amount of storage, only one-fifth the amount of I/O will be performed. 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 performed in-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 is occupied by executable code and more of the partition is made available for sorting records.
Chapter 4. Performance Considerations 4-7
The amount of main storage used by the sort/merge program is a critical factor in the performance of the whole VSE installation. Unicenter CA-Sort adapts itself automatically to the available main storage space depending on the real portion of the sort partition and the size of the main page pool. The calculated size may change based on the total computer load. Both Unicenter CA-Sort and the IBM 5746-SM1 sort print the storage size used in the SYSLST messages: Unicenter CA-Sort : : : : CASD71I STORAGE USED=nnnnn
IBM : : : : 784I STORAGE USED=nnnnn The storage space may be determined by the SIZE= parameter on the EXEC SORT statement 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 sort partition 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 of performance. Excessive use of storage may be avoided by specifying a limiting value in the STORAGE parameter of the CASORT installation macro.
Unicenter CA-Sort will always limit the amount of storage to the smallest of any of the following: ■ 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 CASORT macro, the storage to be used can never be increased above this limit, except through the use of the STORAGE operand on the OPTION control statement, or a value set by a SORTPARM user exit.
The limit specified in the CASORT macro should be based on the processor load and paging activity to minimize the impact on other active partitions.
4-8 Unicenter CA-Sort Systems Programmer Guide
4.3 Unicenter CA-Sort Dataspace Support and the CA90PSTA Utility Program
In order to improve performance, all Unicenter CA-Sort phases are being moved into a dataspace at CA-System Adapter intialization, by the execution of a new utility program called CA90PSTA. This program eliminates all Unicenter CA-Sort phase search and load operations.
CA90PSTA requires approximately 256K of dataspace. If your installation is already using dataspaces, add 256 to the 'DSIZE=' parameter of the SYSDEF DSPACE on your system and allow for one more dataspace in the 'MAX=' parameter. If there are no dataspaces defined in your system, add the following command to your asi proc, to be executed in the BG partition: SYSDEF DSPACE,DSIZE=256K Be aware that if Unicenter CA-Sort SVA eligible phases are loaded in the SVA, they must be loaded prior to CASAUTIL execution.
Warning: If the SVA is reloaded or a PTF is applied to any of the Unicenter CA-Sort phases, then CA90PSTA must be re-executed.
Chapter 4. Performance Considerations 4-9
4-10 Unicenter CA-Sort Systems Programmer Guide
Chapter 5. Running Unicenter CA-Sort Under CMS/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. Space for sort work files will be allocated as CMS files.
Due to the restrictions of CMS/DOS, many of the Phase 0 assignment restrictions which were removed or relaxed when running under DOS/VS or VSE, are restored. Logical units must be preassigned and label records must be properly defined before beginning the Sort/Merge process.
To assist in this effort, Unicenter CA-Sort for CMS/DOS provides several CMS EXECs to set up the necessary DLBL and ASSGN control statements for CMS/DOS. A complete list of the CASDOS EXEC messages is included in the Message Guide, specifically messages CASD601A - CASD657E. In addition, a CMS HELP file is supplied to provide a quick reference in the operation of the EXEC.
Unicenter CA-Sort may be initiated by using the EXEC procedure, by invoking it from another program, or by submitting the necessary CMS/DOS job control statements manually.
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 CASORT macro: 1. Execute CACMSALT, select SDSORT, and change the parameters as required. File CA72A000 ASSEMBLE calls the CASORT macro and contains the default options shown below. (For more information on installation options, refer to the "Installations Options" 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 completes successfully, CASDSORT DOSLIB will be recreated using the installation EXEC CASRDGEN. 4. After verification of successful installation, move the new DOSLIB to its permanent location.
5-2 Unicenter CA-Sort Systems Programmer Guide
5.3 Displaying Unicenter CA-Sort Product Options (SRTCHECK Program)
Follow the steps below to display the Unicenter CA-Sort options currently in effect for CMS/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-Sort options currently in effect. For example: EXECUTION BEGINS... CASD7I Unicenter CA-Sort CMS/DOS VERSION 7.2 GENERATION OPTIONS IN EFFECT CASD71I GENLVL= 868SD CASD72I PACKAGE PREFIX= CA72 CASD73I SYSTEM INSTR SET= 37/43 CASD74I MODEL CLASS= 4341 CASD75I OPSYS= DOS/VS(E) CASD76I MSG= BOTH CASD77I PFIX= YES CASD78I OPT= E CASD79I DYNAM/D= NO CASD71I STORAGE= 4K CASD715I PREOPEN= NO CASD711I DEFDTF= CANCEL
Chapter 5. Running Unicenter CA-Sort Under CMS/DOS 5-3
5.4 Using Unicenter CA-Sort Under CMS/DOS
Some Unicenter CA-Sort functions which are available when executing under VSE are not 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 is ignored under CMS/DOS. ■ CMS/DOS requires that all ASSGN and DLBL/LABELDEF statements be in effect before beginning the Sort/Merge process. Use of the CASDOS EXEC will simplify this process. ■ Unless Unicenter CA-Sort is initiated from another program, the sort/merge control statements must be placed in a fixed-length, 80-byte CMS file. This file must be identified 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 (for example, with a filemode of 4) is being read or written. These types of files are generally created in simulated VSE format by executing a program which contains standard VSE SAM macros (DTFSD/GET/PUT, and so forth) in a CMS/DOS environment. DOS format files may be mixed with CMS format files for input and/or output. ■ 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 not stored with RDWs. However, when Unicenter CA-Sort reads these files, an RDW is built for each record. The Record Descriptor Word is stripped before writing to a CMS variable-length record file. When specifying Sort/Merge control fields, the four-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.
5-4 Unicenter CA-Sort Systems Programmer Guide
The following control statements and keywords are not supported in a CMS/DOS environment: ■ 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 a CMS/DOS environment. If specified, WORK=1 will be assumed by Unicenter CA-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, and NOERASE. ADDROUT may be used with VSAM input files only.
Chapter 5. Running Unicenter CA-Sort Under CMS/DOS 5-5
5.5 Executing Unicenter CA-Sort for CMS/DOS
Unicenter CA-Sort may be executed using any of three methods under CMS/DOS. These include: ■ 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 to view these messages, an ASSGN statement should be issued. If SYSLST will be directed to 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. If Unicenter CA-Sort has been invoked from another program, and that program produces printed output, the output should not be directed to the same CMS file that SYSLST is assigned to, since this could cause some messages to be lost. Use one CMS file for messages produced to the SYSLST logical unit, and ASSGN/DLBL to another file for the report produced by the program.
Unicenter CA-Sort for CMS/DOS will read its control statements from whatever the SYSIPT 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 statements must be passed in a parameter list as described in the Unicenter CA-Sort User Guide.
5-6 Unicenter CA-Sort Systems Programmer Guide
5.6 Applying Maintenance
Although Unicenter CA-Sort program fixes and upgrades will always be provided as a new tape, it might sometimes be necessary to apply a single program fix supplied by Computer 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 5. Running Unicenter CA-Sort Under CMS/DOS 5-7
5-8 Unicenter CA-Sort Systems Programmer Guide
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 if you have a problem with a Computer Associates software product. Each of these procedures is detailed on the following pages.
6-2 Unicenter CA-Sort Systems Programmer Guide
Chapter 6. Troubleshooting 6-3
6.2.1 Collecting Diagnostic Data
In the table below, use the left column to categorize the problem your site has encountered. Then, follow the instructions in the corresponding right column to generate useful diagnostic data.
For Be Sure to Check All Problems The rerun job step (to determine if the problem is an isolated occurrence). If the rerun is successful, a hardware error may have caused the problem. The JCL statements, options and assignments in effect, and the Sort/Merge control statements (to determine if there are any conflicts or problems in coding). If the job has run successfully before, and if so, when the last successful run was made. A change may have been made to the operating system, a master file layout, the data involved, or the invoking program. That you have available the following items or information: ■ All JCL used to run the job, including the Sort/Merge control statements. ■ All SYSLST output, including messages which may have been produced, and a complete partition or supervisor dump if one was generated. ■ A complete list of all messages produced on the console log for the failing job step. All Problems That you have available the following items or information: ■ Knowledge of the release and genlevel being executed. This may be obtained from the execution SYSLST output of CAISERV, which is discussed later under 'CAISERV Utility.' ■ An execution of the failing job step with DIAG specified either on the OPTION control statement or through SYSPARM. The information produced from the DIAG function will often greatly speed the identification and subsequent resolution of any problem reported. When the job is rerun, PRINT=ALL and DUMP should also be in effect. ■ If necessary, the input data sets to the failing sort step should also be kept, in order to reproduce the error and test any proposed fixes.
6-4 Unicenter CA-Sort Systems Programmer Guide
For Be Sure to Check Program-Invoked Listings of all user routines being used at program exits (E15, Sorts and User E35, and so forth) and/or the Assembler, COBOL, PL/I or RPG Exits program being used to invoke Unicenter CA-Sort. These listings should also include link maps.
6.2.1.1 Interpreting Diagnostic Data
When you have collected the specified diagnostic data, write down your answers to the following 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 you take? 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 of the 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 cause and resolve the problem.
Chapter 6. Troubleshooting 6-5
6.2.2 Accessing the Online Client Support Systems
To complement CA Technical Support, Computer Associates provides an online support system, CA-TCC. (CA Total Client Care). This system is provided as a dial-up service to provide you with total service and support. To enroll in this service, contact your CA Client Service Representative.
6.2.2.1 CA-TCC
CA-TCC is a major extension to existing CA support programs. It provides access to the CA centralized client support database by simply dialing into the CA Technical Support system using CompuServe.
CA-TCC provides online access to PTFs and PIBs for all environments. It includes direct problem reporting, tracking capabilities, and a powerful keyword search facility to allow you to locate resolutions to problems and download the resolutions for immediate application. CA-TCC additionally provides electronic mail (CA-eMAIL+) which allows you to contact Computer Associates staff, view product information, and order documentation and other materials online.
To access CA-TCC, you need hardware that can run screen capture software, and that emulates 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 when you enroll in CA-TCC.
CA-TCC service and features are available 24 hours per day, seven days per week, free of charge. There is, however, a nominal hourly charge from CompuServe for use of its network and services.
6-6 Unicenter CA-Sort Systems Programmer Guide
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 Unicenter CA-Sort Technical Support phone number. Outside North America, call your local Computer Associates Support Center during normal business hours. Note: Only your local Computer Associates Support Center can provide native language assistance. Please use English when contacting any North American center.
Emergency phone numbers are also available for after-hours technical support and are listed on the back of the title page of every CA manual. After hours calls should be limited to severity 1 problems.
If you are unable to locate the technical support number you need, call the number listed on the back of the title page in this manual. The operator will record your call and a CA-product Technical Support representative will call you back.
If you are unable to resolve the problem, please have the following information ready before 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. Use the 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-impact condition associated with the product 4 = a question concerning general product utilization or implementation
Chapter 6. Troubleshooting 6-7
6.2.4 Generating a Problem Report
Once a Computer Associates Technical Support representative has determined that your problem requires further investigation, you can use the CAISERV utility to generate a problem report.
6.2.5 CAISERV Utility
The CAISERV diagnostic facility produces a problem report for you to fill out and send in with all problem documentation.
CAISERV also produces a short report on the Computer Associates products that you have installed. You should also send this information to help Technical Support solve your 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.
6-8 Unicenter CA-Sort Systems Programmer Guide
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 FF6439 ------ᑍ ᑍ ᑍ ᑍ ------ᑍ ᑍ 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 Associates Technical Support system and will be tracked from the time it is reported to the time it is resolved.
Chapter 6. Troubleshooting 6-9
On the next page of the problem report, describe the problem you are experiencing. The headings on this page look like this:
COMPUTER ASSOCIATES PROGRAM STATUS REPORT CAISERV-1 PAGE 2
ᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍ ᑍ ᑍ ᑍ COMPUTER ASSOCIATES PROBLEM REPORT FORM ᑍ ᑍ ᑍ ᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍ ᑍ ᑍ ᑍ PROBLEM DESCRIPTION : ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍ ᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍᑍ
6-10 Unicenter CA-Sort Systems Programmer Guide
The last page of the problem report provides a status of the Computer Associates products that you have installed. In most instances, this report includes the product release number, genlevel, and installation options. This is a sample Unicenter CA-Sort report:
CAISERV 1 ᑍ COMPUTER ASSOCIATES PRODUCT STATUS REPORT ᑍ 5/13/97 (MM/DD/YY) 11.28.39 (HH.MM.SS) PAGE 15 CASD7I CA-SORT DOS VERSION 9. GENERATION OPTIONS IN EFFECT CASD71I GENLVL= 24SD9 CASD72I PACKAGE PREFIX= CA9 CASD73I SYSTEM INSTR SET= 37/43 CASD74I MODEL CLASS= 4341 CASD75I OPSYS= DOS/VS(E) CASD76I MSG= BOTH CASD77I PFIX= NO CASD78I OPT= E CASD79I DYNAM/D= YES CURRENT LEVEL RUNNING= 6. CASD71I STORAGE= 4K 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. CASD72I 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 CASD73I ALTSEQ= NONE CASD732I CENTURY WINDOW= 1917-216 | CASD733I DSPSIZE= 124
6.2.5.1 CA90DEVC Utility
The CA90DEVC diagnostic facility produces a device characteristics report for a problematic device. To invoke CA90DEVC, use the following JCL: // ASSGN SYS,device // EXEC CA9DEVC
Chapter 6. Troubleshooting 6-11
6.3 Product Releases and Maintenance
New users of Unicenter CA-Sort are provided with a distribution tape containing the current version of the system. Clients are requested to operate only under currently supported releases of Unicenter CA-Sort
Standard user documentation is also provided to Unicenter CA-Sort users. Updates to this documentation are provided automatically to all clients having current maintenance agreements.
Clients with current maintenance agreements also receive ongoing Unicenter CA-Sort maintenance. When a new release of the system is available, a notice is sent to all current Unicenter CA-Sort clients.
6.4 Requesting Enhancements
Computer Associates welcomes your suggestions for product enhancements. All suggestions are considered and acknowledged. You can use either of two methods to request 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 and return it to Computer Associates.
The DAR system serves as a central receiving point for all enhancement requests.
6-12 Unicenter CA-Sort Systems Programmer Guide
Index
Special Characters D $FIINTR1 module 2-5 Dataspace support, CA90PSTA utility program 4-9 DEFDTF, installation parameter 2-6 DIAG option 6-5 A Disk space management systems 2-3 ALTSEQ, installation parameter 2-12 DISK, installation parameter 2-7 ANALYZE control statement 4-1 DLBL/LABELDEF 5-4 APAR 6-5 DOS SAM 5-4 ASSGN statement 5-1, 5-4 DOS/MVT 2-4 DOSLIB 5-2 DSPIZE, installation parameter 2-14 B DTF determination 2-3, 2-6 BIAS factor 4-3 DTFSD 5-4 Block size 4-5 DYNALOC, installation parameter 2-9 Buffers 4-7 DYNAMD, installation parameter 2-5 DYNAMFI, installation parameter 2-5 C CA-TCC (online support system) 6-6 CA72A000 5-2 E EQUALS, installation parameter 2-6, 4-5 CA90PSTA utility program 4-9 EXCP 4-7 CAISERV 2-2, 6-8 EXEC 5-1 Calculation Exit E15 6-4 of disk work space 4-1 Exit E35 2-7, 6-4 of minimum main storage 4-5 CANCEL 2-6 CASDOS EXEC 5-6 F CASDSORT 5-2, 5-7 FETCH 5-6 CASORT macro File size estimation 4-1 assembly 2-1 generation example 2-16 storage limit 4-8 G CASRDGEN 5-2, 5-7 General register contents 3-3 CCW 4-5 CHALT, installation parameter 2-13 CHECK, installation parameter 2-7 I CHKPT|CKPT 5-5 IDAL 4-5 CISIZE 2-3 IJSYSLS 5-6 CMS exec 5-1 In-core sort 1-1, 4-3 CMS FETCH command 5-6 Initiation 1-1 CMS/DOS 5-1, 5-4 INPFIL 5-4, 5-5 Computer model codes 2-15 INREC 4-5 Installation Options 5-2 Interface SORTPARM 3-1 Unicenter CA-Dynam/D 2-5, 2-9
Index X-1
Interface (continued) Product Unicenter CA-Dynam/FI 2-5 Support Directory 6-6 INVCNCL, installation parameter 2-9 Program fix 5-7 Invoked operation 1-1 PTF 6-5 INVPRNT, installation parameter 2-3 PUTLEVEL 6-6 ISAM 5-5 R J RC, installation parameter 2-11 JCLPRNT, installation parameter 2-3 RDW 5-4 RECORD control statement 4-4 Record counts 2-7 L RESERVE, installation parameter 2-5 Labels, use in DTF determination 2-6 RETURN 3-3 LIOCS modules 3-3 Return address 3-3 LST 2-2 S M SAVE 3-3 Main storage 2-4, 4-5 Save area 3-3 Merge order 1-2 SIZE keyword 4-1, 4-8 Message routing 2-2 SORTPARM exit 3-1, 4-8 Mixed DASD support 2-7 SPECIAL, installation parameter 2-11 Modal record length 4-4 SRD72PTF 5-7 Model Codes 2-15 SRTCHECK 5-3 MODEL, installation parameter 2-2 STORAGE MODS control statement 4-5 installation parameter 2-4 MSG, installation parameter 2-2 OPTION satement keyword 4-8 OPTION statement keyword 2-4 Storage requirements O minimum 4-5 Online support systems 6-6 optimum 4-7 OPSYS, installation parameter 2-4 Support, online systems 6-6 OPT, installation parameter 2-2, 4-2 SVA 4-5, 4-7 Optimim Main Storage 4-7 SYSIPT 5-6 Optimization 4-1, 4-2, 4-4 SYSLST 5-6 OPTION 2-4, 4-8 SYSPARM 6-5 OUTFIL 5-4 U P Unicenter CA-Dynam/D interface 2-5, 2-9 Page fixing 2-3, 3-1 Unicenter CA-Dynam/FI interface 2-5 Paging 4-8 Performance 2-9, 4-1, 4-7 PFIX, installation parameter 2-3, 5-4, 5-7 V PHASE, installation parameter 2-2 VSE support 1-1, 2-4 PREOPEN, installation parameter 2-3 PRF 6-7 PRINT 6-4 W Private CCW Translation 2-3 WKASN, installation parameter 2-9
X-2 Unicenter CA-Sort Systems Programmer Guide
WKXTNTS, installation parameter 2-11 WORK 5-5 Work file device types 4-5 dynamic allocation 2-9 logical units 2-9 use of the DISK installation parameter 2-7 use of the WKASN installation parameter 2-9
Y Y2PAST, installation parameter 2-14
Index X-3