I always encourage SYNCSORT customers using MICS to reach-out to SYNCSORT technical support for performance tuning guidance with their MICS $ORTPARM DD parameter definition. Consider that the MICS-default (distributed version) SYNCSORT PARMS member provided is basic and can always be improved for the unique sort-environment, such as with a MICS/SAS environment where there are many large/small sorts performed in a given job-step (for example, the VSCORET= parameter along with an increased JOB/STEP REGION-size, and apparently some more-recent parameter settings DSM/DSMWEND.) Also, beyond the MFX/SYNCSORT basic-install, an optional feature can be licensed with SAS-interface PROC SYNCSORT, as well as the MFX/SYNCSORT feature for zIIP CP/core enablement.
Other SYNCSORT/DFSORT performance tuning opportunities can be realized simply with having a sufficient number of pre-allocated //SORTWKnn JCL DD statements and specifying key DD parameters DSNTYPE=LARGE and also both secondary as well as primary SPACE. Do consider that MICS JCLDEFC/JCLDEF parameters SORTUTILITY, SORTCYL, SORTSMSPARMS, and SORTWKNO are provided to ensure that the MICS-generated JCL PROCs and jobstreams are always configured optimally, especially after periodic maintenance and occasional JCLGEN processing. You don't want to be editing MICS PROCs and/or JCL-jobstreams directly -- ask MICS support for guidance with how you can ensure MICS JCL tailoring is performed without fear for "what might get restored if I re-gen this unit-level MICSDBx JCL PROC?
Of course, any MICS-tailoring must be tested, verified, and applied using strong LOCALMOD coding techniques, such as to avoid back-leveling any directly edited-member with maintenance and/or periodic JCLGEN (execution or PROC JCL-member, MICS/SAS CONFIG, or other tailoring method such as MICS-distributed $ORTPARM/SORTCNTL "sample" parameter member used with the host-SORT package.)
Scott Barry
SBBTech LLC
Original Message:
Sent: 12-08-2021 07:14 AM
From: Scott Barry
Subject: Parms(SyncSort)
According to an MFX 3.1 Install Guide (found with an Internet search), suggesting checking execution or PROC JCL executed, either looking for the SPYSET DD or directed to //SYSOUT DD – also, verify the $ORTPARM DD parameters (or possibly even a JCL EXEC PARM=) being passed to MFX/SYNCSORT and possibly there is a DEBUG parameter specified?
Scott Barry
SBBTech LLC
Original Message:
Sent: 12-07-2021 12:53 PM
From: Michel Lavoie
Subject: Parms(SyncSort)
Hello,
There was a maintenance of our system last week and since that time in the MICS logs there has appeared a SPYSET sysout which contains hundreds of thousand lines, yet we have not changed our syncsort parameter at the level of l 'unity. How the SPYSET appeared. Thank you