Downloading and restoring SOUL files
This page provides Help for downloading from the "SOUL files for Sirius Software Inc." page that is accessed from the Rocket website Rocket M204 Customer Care page.
What is RKTools?
Formerly known as UL/SPF, RKTools is a family of tools that enhance programmer-productivity and
enable performance monitoring, sophisticated journal querying and other
programmer, DBA and system administrator
activities inside a Model 204 online. RKTools is implemented as a
set of application subsystems (APSYs), written in SOUL. RKTools must
be installed in each Online where its features are needed. Installation
requires Rocket M204 SOUL code, some files
that must be allocated locally, and the creation of the necessary APSYs.
The source code for all RKTools subsystems is in the SIRIUS procedure file, which must be physically allocated to the Online for the installation process.
For versions of Model 204 prior to 7.5, the Sirius Mods must also be installed in the target online prior to the installation of RKTools.
How do I get the RKTools installation file?
SOUL code for the RKTools product is distributed in the form of a dump of the SIRIUS file from the Rocket M204 support site.
On most browsers a fly-out menu will provide options to
Save Link As... or Save Target As... or something similar.
After selecting a target directory, the file will download in binary format.
Alternatively, the left mouse button can be clicked on the link for a dump file. This will usually result in the browser prompting the user whether the file should be saved, where it should be saved and under what name. Download times depend on the speed of your connection.
Aternatively, the dump file can be e-mailed as an attachment by clicking on the e-mail link above. The attached binary should be saved to a local file and then uploaded to the mainframe exactly as if it had been downloaded directly. E-mail delivery can be useful if your firewall disallows web downloads.
How can the dump file be uploaded to the mainframe?
The Sirius dump file must then be uploaded to your MVS, VM, or VSE system on your mainframe.
Any file transfer mechanism can be used including FTP and IND$FILE,
but regardless of the transfer mechanism some rules must be observed.
First, the dump files contain binary data, and so must be transferred as binary. That is, no translation from ASCII to EBCDIC must occur as a result of the upload.
Second, the format and LRECL of the file must be specified during
the upload. This is because most workstation systems (including
Windows, Mac OS, and Unix) do not have a concept of file formats
and LRECLs. The format of the uploaded file must be F and
the LRECL must be 6184. Under MVS and VSE the blocksize must be 6184.
When using FTP, the characteristics (RECFM, LRECL, and BLOCKSIZE) of
the uploaded file can be set with the SITE and LOCSITE
FTP commands. The SITE command should be used if the FTP client
is on the workstation and the server is on the mainframe. In this case
the SITE command might have to be sent as a "quote" to the mainframe.
How this is done, depends on your workstation's FTP client.
The LOCSITE command should be used if the FTP client is on the mainframe and the server is on the workstation.
How can the uploaded files be installed on the mainframe?
Once the dump file is uploaded to your mainframe, use the standard Model 204 RESTORE command to restore the dump file to a Model 204 file with a DDNAME of SIRIUS.
File Size: The SIRIUS file must be allocated with at least 4200 Model 204 pages.
The rest of the installation process for the Sirius Software User Language products is described in the UL/SPF installation guide, including ancillary files that must be allocated.
Applying maintenance
The uploaded files will contain all the latest maintenance. As such, no maintenance need be applied to the uploaded file. Subsequent fixes can be applied by downloading User Language fixes, loading them into the SIRFIXES file and applying them to the appropriate Model 204 file with SIRFIX. Most sites find it easier to return to this page and re-download a new copy of the SIRIUS file, as the downloadable copy always has the latest maintenance applied.
DICDIST and M204PROC
The file DICDIST (Dictionary distribution) contains all of the subsystem procedures for the standard Rocket subsystems - SUBSYSMGMT, FILEMGMT, DICTIONARY, DOCUMENT, DICTADMIN, DICTREPORT and XREF. A dump of the DICDIST file is downloaded, in binary, from the Rocket-M204 web site, uploaded to your z/OS system and then used to RESTORE the DICDIST file. Upload the DICDIST dump file into a z/OS dataset (DSN=your.V750.DICDIST.DUMP.M204) which you have previously allocated with LRECL=6184,BLKSIZE=6184,RECFM=FB,SPACE=(6184,2000) then run the following job:
DDPRCLOD job
//DDPRCLOD EXEC PGM=BATCH204,REGION=0M,PARM='SYSOPT=176' //STEPLIB DD DISP=SHR,DSN=your.V750.LOADLIB //CCASTAT DD DISP=SHR,DSN=your.CCASTAT //CCAPRINT DD SYSOUT=A //CCAAUDIT DD SYSOUT=A //CCASNAP DD SYSOUT=A //SYSUDUMP DD SYSOUT=A //M204PROC DD DISP=SHR,DSN=your.M204PROC.M204 //DICDIST DD DISP=(NEW,CATLG,DELETE),DSN=your.V750.DICDIST.M204, // DD SPACE=(6184,2000),UNIT=3390,VOL=SER=yourvol //DICDDUMP DD DISP=SHR,DSN=your.V750.DICDIST.DUMP.M204 //CCAIN DD * LITBL=3000,LFSCB=7000,NFILES=10,LSTBL=10000,TEMPPAGE=1000 LOGON SUPERKLUGE PIGFLOUR CREATE FILE DICDIST PARAMETER BSIZE=1,CSIZE=1,DSIZE=1 END OPEN DICDIST RESTORE 192 FROM DICDDUMP OPEN DICDIST pw OPEN M204PROC pw IN FILE DICDIST COPY PROC ALL TO FILE M204PROC OLDDATE REPLACE IN M204PROC DISPLAY LIST CLOSE ALL LOGOUT EOJ // /* End of DDPRCLOD *******