Software delivery - syncsort_cobol_migration_manager - syncsort_clone_center - syncsort_space_recovery_system - syncsort_scc_monitor - syncsort_simulate_2000 - syncsort_allocation_control_center - Latest

Syncsort™ Storage Management Product Installation Guide And DIF User Guide
Product type
Software
Portfolio
Integrate
Product family
Syncsort™ software
Product
Syncsort™ Storage Management > Syncsort™ Cobol Migration Manager
Syncsort™ Storage Management > Syncsort™ Clone Center
Syncsort™ Storage Management > Syncsort™ Space Recovery System
Syncsort™ Storage Management > Syncsort™ SCC Monitor
Syncsort™ Storage Management > Syncsort™ Simulate 2000
Syncsort™ Storage Management > Syncsort™ Allocation Control Center
Version
Latest
ft:locale
en-US
Product name
Syncsort Storage Management
ft:title
Syncsort™ Storage Management Product Installation Guide And DIF User Guide
Copyright
2023
First publish date
1991
ft:lastEdition
2026-01-22
ft:lastPublication
2026-01-22T05:50:39.722000
L1_Product_Gateway
Integrate
L2_Product_Segment
IBM Infrastructure
L3_Product_Brand
Precisely Syncsort
L4_Investment_Segment
Mainframe
L5_Product_Group
Mainframe Storage Optimization
L6_Product_Name
Syncsort Storage Management

The following procedure explains how to download software from the Precisely Data Experience (PDX).

  1. On the PDX portal, navigate to My Software Products
  2. From My Software Products, download your active software subscriptions.
    Tip: You must be signed in to the PDX portal to access My Software Products.

When you purchase Software from Precisely, the Fulfillment team "provisions" the primary contact user or users to enable download from the PDX and sends an email with instructions for creating a password to access the site.

You can choose to download the purchased software by selecting any of the supported Data formats relevant to the Software. Users typically receive an email from Precisely when new Software releases are available for download. Provisioned users can also typically access previously downloaded versions of Software at the PDX.

If the software download link is not accessible through this portal, you may reach out to Customer Support for additional assistance.

License Key

Companies performing a product evaluation need to request license keys from Customer Support to activate the SCC products.

Software

When downloaded from the PDX website, the distribution libraries have been compressed into a self-extracting ZIP file (.exe) which can be expanded on a PC.

Tip: For installations that deny .exe downloads through a web browser, two other distributions are provided.

The .zip file contains the same files as the self-extracting .exe file, while the _distronly.zip file omits all .exe and .bat files from the download.

Once the product installation files are available on a PC, the product distribution files can then be uploaded to your host system. To continue with the installation process, refer to Transferring PC distribution files to your host below.

Documentation

All the SyncsortTM Storage Management Software documentation is available at the Precisely Help Center. The product guides can be downloaded in PDF format from the Precisely Help Center using Print this topic option.

Note: You must be logged in to access the Print this topic option.

To access all site capabilities, click Sign In at the top-right corner of the Precisely Help Center, and use your Precisely Customer or Partner Community sign-in credentials.

If you do not have a Community account, register at https://rc.precisely.com/customer-self-registration-portal.

Service level and product release information

When a new set of distribution libraries is created, the build process assigns the current Julian date as the software's Service Level. The third level qualifier on the distribution libraries identifies the service level. For example, the following data set is at service level 21054.

DTS.R71.SL21054.LOADLIB

After installation on your mainframe system, the service level and product release information for each product can be found in DTS.R71.SLyyddd.LOADLIB(DTSRELI).

Tip: Use the service level in the distribution data set names you create on your system.

Electronic delivery of distribution data sets

When the SCC products are packaged for electronic delivery, the product distribution libraries are "unloaded" to sequential data sets with the XMIT TSO Command processor. This allows the distribution libraries to be sent to other z/OS systems. The following "unloaded" distribution files are transmitted to the host:
LOADLIB.XMI   unloaded version of DTS.R71.SLyyddd.LOADLIB
INSTLIB.XMI   unloaded version of DTS.R71.SLyyddd.INSTLIB
ISPFLIB.XMI   unloaded version of DTS.R71.SLyyddd.ISPFLIB
SAMPLIB.XMI   unloaded version of DTS.R71.SLyyddd.SAMPLIB
RPTLIB.XMI    unloaded version of DTS.R71.SLyyddd.RPTLIB

During the install process, a batch job will allocate the "real" distribution libraries, and use the TMP to RECEIVE the "unloaded" files and populate the real distribution files. The install process will delete the "unloaded" versions of the distribution files. After the batch job completes, the following SCC distribution data sets can be found on the volume you selected:

DTS.R71.SLyyddd.LOADLIB
DTS.R71.SLyyddd.INSTLIB
DTS.R71.SLyyddd.ISPFLIB
DTS.R71.SLyyddd.SAMPLIB
DTS.R71.SLyyddd.RPTLIB

Distribution data sets

The following list shows sample distribution libraries and the storage attributes. These are the data sets that should exist on your host system after completing the software installation covered in this chapter.

Note: You do not need to pre-allocate these data sets.

DTS.R71.SLyyddd.LOADLIB

The load library for all products.

BLKSIZE:6144 RECFM:U
SPACE: CYL(5,2,80)

DTS.R71.SLyyddd.INSTLIB

This file contains the installation library. This library contains installation JCL and the parameter information intended for the DIF parameter library:

DTS.R71.PARMLIB

BLKSIZE:3120 LRECL:80 RECFM:FB
SPACE: CYL(1,1,40)

DTS.R71.SLyyddd.ISPFLIB

This file contains the ISPF members used for the products.

BLKSIZE:3120 LRECL:80 RECFM:FB
SPACE: CYL(10,2,80)

DTS.R71.SLyyddd.SAMPLIB

This file contains the sample library for rules developed for the products. 
BLKSIZE:3120 LRECL:80 RECFM:FB
SPACE: CYL(5,2,80)

DTS.R71.SLyyddd.RPTLIB

This file contains the report library used for creating reports for the products.

BLKSIZE:3120 LRECL:80 RECFM:FB
SPACE: CYL(5,2,80)

Transferring PC distribution files to your host

This section documents the methods of moving the distribution libraries from your PC to your host. To use the distribution facilities documented in this section, you must have:

  • a personal computer with access to your host system
  • the ability to file transfer text and binary files to your host system.

    There are two methods of installation:

    • If you can FTP files from your PC to the host, the FTPINSTW.EXE and FTPINST.BAT commands provide the quickest installation procedure.
    • Otherwise, you can use the file transfer facility in your TN 3270 Emulation client.
    Note: The following installation procedure assumes you already received the self-extracting file via the Internet or email, and the file has been expanded in an empty directory.

Installation via FTPINSTW.EXE

If your host environment runs an FTP Server, the FTP Installation application (FTPINSTW.EXE) can be used to create the distribution libraries on your z/OS system.

FTP Installation Application

This 32-bit Windows application automatically allocates and transfers the "unloaded" distribution libraries to your host. The program then builds and submits a job to:

  • allocate the "real" distribution libraries
  • run the TMP to RECEIVE the unloaded files into the distribution libraries
  • delete the "unloaded" distribution files

    The FTP Installation application can only be run on a modern Windows-based system. As an alternative, see the FTPINST.BAT installation procedure documented in the next section. To activate the installation program, examine the directory containing FTPINSTW.EXE, and double-click on the file.

    Note: The FTPINSTW.EXE program must reside with the other distribution files.

The FTP Installation application provides an easy install interface for the user. The single form requires:

  • IP address or domain name of your z/OS FTP Server
  • Userid/Password
  • job card statement(s)
  • HLQ and a Volume or Storage Class for the distribution data sets

If you don't know the IP address of your FTP Server, try browsing SYS1.PROCLIB(TCPIP).

Note: The procedure name and location are installation dependent, but the procedure name is fairly typical. Once you've located the TCPIP procedure, the PROFILE DD statement points to the TCPIP profile data set. Browse the data set, and scan for the HOME statement which contains the IP address.
HOME
199.72.47.195 ETH1

A TSO Userid, Password, and JOB card are required for the FTP install process. Symbolic substitution will be performed on any %userid% and %password% variables in the job card. Also, USER= and PASSWORD= parameters are required on the job card, and you might also want to route the output to a held printer queue.

You only have to enter the information the first time you use the application. The installation program saves the user input for subsequent calls in two files: FTPINSTW.INI and FTPINST.JOB. An installation FTP log is also created in FTPINSTW.LOG. These files are saved in the user application directory - usually c:\Users\username\AppData\Roaming\DTS or c:\Users\username\AppData\Local\DTS.

Note: If you use the FTPINSTW.EXE application to install the same SCC service level, the host libraries will be refreshed by the procedure.

Installation via FTPINST.BAT

If your host runs an FTP Server and your PC denies access to the FTPINSTW application, the FTPINST.BAT file can be used to install the SCC distribution libraries. FTPINST builds an FTP script to create the "unloaded" distribution libraries on the host system. The batch file then builds and submits a job via FTP to allocate the distribution libraries and RECEIVE the unloaded files.

Before running the FTPINST batch file, you must modify the JOBCARD.TXT member so it contains a valid job card for your installation. The USER= and PASSWORD= parameters are required, and you might also want to route the output to a held printer queue.

Note: If you get JCL errors on the submit, make sure that you have a carriage return after the last JCL statement in JOBCARD.TXT. Also, when installing from the CD, the job card information must be created on your hard-drive, and you must use a fully qualified member name in the last FTPINST parameter.

The sample JOBCARD.TXT file:

//jobname JOB REGION=1M,USER=userid,PASSWORD=password
/*ROUTE PRINT FETCH

After modifying the jobcard.txt file, you can issue the FTPINST command. Open a DOS session and default to the directory containing the distribution files. From the DOS prompt issue the FTPINST command. Since most of the parameters are used in JCL submitted to your host, you must code the parameters in upper-case.

The FTPINST batch file has six positional parameters:

  1. HLQ of the distribution libraries.
    Note: This parameter can contain multiple qualifiers (i.e. VENDOR.DTS). Also, this parameter is case dependent and should be entered in uppercase.
  2. IP address or Domain name of the z/OS FTP Server
  3. TSO Userid for logon
  4. TSO Password for logon
  5. The volume name for new allocations.
    Note: This parameter is case dependent and should be entered in uppercase.
  6. Name and location of the file containing the JOB card information (i.e. c:\temp\jobcard.txt).

Sample execution:

ftpinst DTS 199.72.47.195 USER1 PASS1 DTS001 JOBCARD.TXT

After using the FTPINST installation method, you can further automate the procedure by building another batch file that executes the FTPINST command with your installation parameters. For example, you could create an INST.BAT member that executes the command above. When you download another SCC Service Level, expand the .exe file in the same directory as the INST.BAT and JOBCARD.TXT files, but don't overwrite your job card file. The next installation can then be done by simply issuing INST.

Note: If you use the FTPINST command on the same SCC service level, the host libraries will be refreshed by the procedure.

Installation via 3270 emulation

This installation method uses the 3270 emulation file transfer facilities to build the installation libraries on your host. Please examine the README.TXT file for detailed instructions on the process required for the product. The following steps are generalized instructions for electronic delivery.

  1. STEP 1: Start your 3270 emulation software on your PC. LOGON to your host system.
    Note: Stay in READY mode - do not enter ISPF.
  2. STEP 2: Use your 3270 emulation software to file transfer the ALLOCATE and RECEIVE files to your host system. Since the members contain character data, send the members as text files - use the ASCII and CRLF options on the file transfer and Record Format = Default. A sample SEND command follows: SEND ALLOCATE 'userid.ALLOCATE' ASCII CRLF SEND RECEIVE 'userid.RECEIVE' ASCII CRLF
  3. STEP 3: Go to your TSO session and edit 'userid.ALLOCATE'. Use the JCL to pre-allocate the data sets required for installation. Add an appropriate job card, select a volume for the data sets, and submit the JCL to allocate the data sets.
  4. STEP 4: Use your 3270 emulation software to file transfer the unloaded distribution files to your host system. The files require a binary file transfer. A sample SEND command for the SCC distribution load library follows. The README.TXT file will contain the list of distribution libraries to transfer to your host system. 
    SEND LOADLIB.XMI 'DTS.R71.LOADLIB.XMI'
  5. STEP 5: Edit 'userid.RECEIVE'. The JCL executes TSO in a batch environment. This job uses RECEIVE commands to reload the distribution libraries created by the ALLOCATE job. Add an appropriate job card, modify the data set names to those used in Step 3, and submit the job.
    Note: The RECEIVE job will always get a return code of zero. Please examine the job output to ensure that the data sets were loaded correctly. If the RECEIVE commands did not work correctly, you may want to examine the file transfer options in your 3270 emulation software and retry step 4. Using "screen buffered" transfers instead of "structured fields" often solves file transfer problems on binary files.
    Warning: If the target libraries already contain members, the IEBCOPY performed by the RECEIVE will replace existing members.
  6. STEP 6: The distribution libraries have now been loaded on your host system. You can now delete the "unloaded" distribution libraries. The README.TXT file will contain the list of "unloaded" distribution libraries that can be deleted.