Template:SirTune installation

SirTune can be installed from a product tape or can be installed from an object deck downloaded from the Rocket Software web site. Installation from tape is described in MVS installation and CMS Installation, while installation from the web is described in Installation from the web. All SirTune distributions come with all maintenance pre-applied: up to the time the tape was cut for tape installations, and up to the time the object deck was downloaded for web installations.

As of Version 7.2, reporting is performed by a User Language program that is distributed in the SIRIUS file as part of the UL/SPF product family. If your site uses UL/SPF, verify both of the following:

1. You have UL/SPF Version 7.2 or later installed,
2. File SIRIUS contains the program SIRTUNEREPORT.

If your site is not licensed for UL/SPF, you are still authorized (as a user of Fast/Unload) to download the SIRIUS file. You can download the SIRIUS file from the Rocket website using the "Download User Language files" link on the Support page (http://sirius-software.com/support.html). If you are not a UL/SPF customer, you don't need to do the entire UL/SPF installation: just download and restore the SIRIUS file, and make it available to your SIRTUNE Report jobs.

If you are a user of a previous version of SirTune, see the SirTune Release Notes for the version you are installing. This document is available on the Rocket Software web site Documentation page. The Release Notes highlight changes in the new version, and they list any compatibility issues with the previous version.

Installation from the web

You can download the SirTune object files from the Rocket Software web site (http://m204.rocketsoftware.com/). The download process requires a userid and password.

1. Click the Support navigation link to go to the Customer Service page (https://support.rocketsoftware.com/rsp-portal/rsp/login), a public page that explains how to get the required userid and password and that also contains links to the various download pages.
2. Click the Download object files link to go to a protected page (https://m204.rocketsoftware.com/maint/objlist) that contains a dynamically-generated list of the various Model 204 add-on products that you may download.

   The page also contains a Click here link that causes the page to be re-displayed with detailed download and installation instructions. These instructions supersede any information in this manual.

3. On the Download object files page, select the link(s) to the currently available SirTune object file(s) for the version you require.

   Clicking a link generates an object file for SirTune that is pre-configured for your site, with all maintenance and authorization ZAPs applied. The "Save As" dialog that displays lets you indicate where the object files are to be saved.

   Note: As of Sirius Mods version 6.9, the "SirTune" object file is integrated into the "Sirius Mods" object file, so to install the latest version of the SirTune components:

   1. Select the "Sirus Mods" link (V6.9 or higher) for the appropriate version of Model 204.
   2. Select the most recent "SirTune Report Generator" link.
   3. If you are running under CMS, select the most recent "SirTune Data Logger" link.

   For earlier versions of the SirTune components, select the appropriate V1.x "SirTune" and "SirTune Report Generator" links, and optionally, for CMS users, the V1.x "SirTune Data Logger" link.

   Running an earlier version of SirTune with Sirius Mods version 6.9 or later is not recommended, since older versions of SirTune are not upgraded to work with new versions of Sirius Mods or Model 204.

MVS installation

SirTune is distributed on a magnetic tape. This magnetic tape has three standard labeled files. These three tape files are:

• SIRIUS.LIB
• SIRIUS.LOAD
• SIRIUS.ULSPF (this file is not used by SirTune)

To install SirTune, load the files from tape onto disk. The tape contains SirTune and any other Sirius products you have ordered. The space allocations are sufficient regardless of how many products you will be loading.

The following JCL performs the load:

//SIRTUNEL JOB (0),'Bart Simpson',MSGCLASS=A,CLASS=C,NOTIFY=BART //* //* Load Sirius products from tape //* //IEBCOPY EXEC PGM=IEBCOPY,REGION=0M //T1 DD UNIT=TAPE,VOL=SER=SIRIUS,LABEL=(1,SL),DISP=(OLD,PASS), // DSN=SIRIUS.LIB //T2 DD UNIT=TAPE,VOL=SER=SIRIUS,LABEL=(2,SL),DISP=(OLD,PASS), // DSN=SIRIUS.LOAD //T3 DD UNIT=TAPE,VOL=SER=SIRIUS,LABEL=(3,SL),DISP=(OLD,PASS), // DSN=SIRIUS.ULSPF //* //D1 DD DISP=(,CATLG),DSN=SIRIUS.LIB,UNIT=SYSDA, // SPACE=(CYL,(10,2,5)) //D2 DD DISP=(,CATLG),DSN=SIRIUS.LOAD,UNIT=SYSDA, // SPACE=(CYL,(5,0,2)) //D3 DD DISP=(,CATLG),DSN=SIRIUS.ULSPF,UNIT=SYSDA, // SPACE=(CYL,(25,0,2)) //SYSPRINT DD SYSOUT=* //SYSIN DD * COPY I=T1,O=D1 COPY I=T2,O=D2 COPY I=T3,O=D3 /*

The job card and possibly the output data set names must be changed to conform to local standards.

After loading the two tape files, SirTune is ready to use. The first tape file contains some sample jobs, object decks used in building SirTune, and a member called ZAP that contains a list of all ZAPs that have been pre-applied to the object decks and load modules. The sample jobs in SIRIUS.LIB are:

LNKTUNE	A job that can be used to relink the SIRTUNE load module if necessary. A pre-linked version is shipped in SIRIUS.LOAD.
LNKTUNER	A job that can be used to relink the SIRTUNER load module if necessary. A pre-linked version is shipped in SIRIUS.LOAD This module is deprecated as of Version 7.2 because SIRTUNER is no longer supported.
RUNTUNER	A sample job that can be used to run SIRTUNER.

All these sample jobs should be modified to conform to local requirements.

As part of the installation process for SirTune version 1.5 and earlier: This module is deprecated as of Version 7.2 because SIRTUNER is no longer supported.

• It might be desirable to move the SIRTUNE load module in SIRIUS.LOAD into a library that will allow access from ONLINE jobs.
• If the ONLINE(s) to be monitored run APF authorized, move SIRTUNE to an APF authorized library so SIRTUNE's monitoring of the ONLINE(s) does not remove the Model 204 load module's APF authorization. If SIRTUNE's RESTART command is to be available, both SIRTUNE and the Model 204 load module must be APF authorized.
• If the ONLINE(s) to be monitored run non-swappable, add SIRTUNE to the program properties table (defined in SCHEDxx in SYS1.PARMLIB) as non-swappable, or rename SIRTUNE to something that is already non-swappable.
• If SIRTUNE is to be used to monitor both swappable and non-swappable load modules, an alias should be created for SIRTUNE. Either the name SIRTUNE or its alias must then be added to the program properties table as non-swappable. The name (SIRTUNE or its alias) that is added to the program properties table should be used to invoke SIRTUNE for the non-swappable load modules, and the other name should be used to invoke SIRTUNE for swappable load modules.

An object deck called IFINTF is distributed in SIRIUS.LIB that, if linked with one or more IFAM2 programs, will allow the IFCHUNK reports to be produced for any jobs using those IFAM2 programs.

CMS Installation

SirTune is distributed on a magnetic tape. This magnetic tape has one physical file made up of multiple logical files. The SirTune distribution tape is in VMFPLC2 format.

To install SirTune:

1. Allocate a minidisk with sufficient space to contain all the Sirius products you ordered. Refer to the tapemap shipped with your installation package for the actual number of blocks required, or allocate a minidisk large enough to hold all Rocket add-on products (about 3,400 4K blocks).
2. Mount the SirTune distribution tape on a tape drive, and attach that tape drive to the installing virtual machine as virtual address 181.
3. Access the SirTune minidisk as A, then type the following to load all the files required to run SirTune:

   TAPE REW VMFPLC2 LOAD

   Included in the loaded files are object decks (with filetype TXTTUNE), load modules (with filetype MODULE), and installation and sample execs (with filetype EXEC).

   The execs on the distribution tape are listed below.

   Note: It is essential that the CMICONV exec (described below) be run before running SIRTUNE.

   BLDTUNE	An exec that can be used to relink the SIRTUNE load module, if necessary. A pre-linked version is shipped on the tape. Since SIRTUNE is linked for XA or ESA versions of CMS, run this exec if running a 370 version (Release 5 and earlier) of CMS.
   BLDTUNED	An exec that can be used to relink the SIRTUNED load module, if necessary. A pre-linked version is shipped on the tape. Since SIRTUNED is linked for XA or ESA versions of CMS, run this exec if running a 370 version (Release 5 and earlier) of CMS.
   BLDTUNER	An exec that can be used to relink the SIRTUNER load module, if necessary. A pre-linked version is shipped on the tape. Since SIRTUNER is linked for XA or ESA versions of CMS, run this exec if running a 370 version (Release 5 and earlier) of CMS. As SIRTUNER is no longer used as of Version 7.2, this feature is deprecated.
   RUNTUNER	A sample exec that can be used to run SIRTUNER. As SIRTUNER is no longer used as of Version 7.2, this feature is deprecated.
   SIRTUNED	A sample exec that can be used as the PROFILE EXEC for the SIRTUNED virtual machine.
   SIRTUNEF	A sample exec that can be used on the SIRTUNED virtual machine. For more information, see SirTune data collection under CMS.
   SIRTUNEA	A sample exec that can be used on the SIRTUNED virtual machine. For more information, see SirTune data collection under CMS.
   CMICONV	An exec that modifies the load addresses of 'M204CMI TXTLIB' members. It must be run once, before you bring up SirTune. The TXTLIB created by this exec should replace the original, or it should be moved to a disk accessed before the original M204CMI TXTLIB. If SIRTUNE is run against a version 3.2 or later ONLINE without running CMICONV, a member from M204CMI TXTLIB will overlay part of the Model 204 load module, resulting in a likely 0C4 or 0C1.

4. After loading the tape files:
   1. If SirTune is version 1.5 or earlier, move SIRTUNE MODULE to a disk that can be accessed by the Model 204 service machines.
   2. Move SIRTUNER MODULE SIRTUNER is not used as of Version 7.2, so this is no longer necessary. to a disk that can be accessed by any user that might wish to produce SIRTUNER reports.
5. Create virtual machine SIRTUNED, and give it access to the appropriate load modules and execs.
   1. SIRTUNED requires the following:
   • PROFILE EXEC (similar to SIRTUNED EXEC from the tape)
   • SIRTUNEA EXEC (similar to SIRTUNEA EXEC from the tape)
   • SIRTUNEF EXEC (similar to SIRTUNEF EXEC from the tape)
   • SIRTUNED MODULE
   2. To run SIRTUNED under the CMS interface (making it possible to write sample data to OS format minidisks), give SIRTUNED access to the M204CMS module shipped with Model 204.

   For more details on setting up SIRTUNED, see SirTune data collection under CMS.

See also

• SirTune introduction
• SirTune data collection under MVS
• SirTune data collection under CMS
• SirTune data collection statements
• SirTune MODIFY and SMSG commands
• SirTune report generation
• SirTune reports
• SirTune user states
• SirTune and Model 204 quad types
• SirTune statement wildcards
• SirTune date processing