|
|
| (31 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| <var class="product">[[UL/SPF]]</var> (the User Language System Productivity Facility) is a set of APSY subsystems running inside a <var class="product">Model 204</var> Online that provide full-screen and web-based tools to aid programmers, DBAs, and system managers to handle the complexities of <var class="product">User Language</var> and file and system management.
| | #REDIRECT [[RKTools installation]] |
| | |
| Installing <var class="product">UL/SPF</var> requires downloading the SIRIUS file and restoring it to your environment, setting up some subsidiary <var class="product">Model 204</var> files, and verifying that the environment has the appropriate parameter settings.
| |
| | |
| Upgrades to <var class="product">UL/SPF</var> can almost always be handled by restoring a fresh copy of the SIRIUS file.
| |
| | |
| ==A summary of the UL/SPF installation steps==
| |
| The following checklist specifies in brief the steps to follow installing
| |
| <var class="product">UL/SPF</var>, whether for MVS or CMS.
| |
| The sections [[Installing UL/SPF under MVS]] and [[Installing UL/SPF under CMS]]
| |
| describe these steps in greater detail for each operating system.
| |
| <ol>
| |
| <li>Install and link the <var class="product">Sirius Mods</var> as described in the <i>Sirius
| |
| Mods Installation Guide</i>.
| |
| <var class="product">UL/SPF</var> requires a matching or greater version number of the <var class="product">Sirius Mods</var>.
| |
| | |
| <li>Allocate the space required for the <var>SIRIUS</var> dataset,
| |
| and <var>RESTORE</var> it from tape, where they are stored in <var>DUMP</var>
| |
| format, or from the <var>DUMP</var> files found on the website.
| |
| <p>
| |
| In addition, there may be any number of other datasets required for
| |
| the <var class="product">UL/SPF</var> components you are installing.
| |
| These are listed in [[Installing UL/SPF under MVS#Installation checklist (MVS)|"Installation cheecklist (MVS)"]]
| |
| and [[Installing UL/SPF under CMS#Installation checklist (CMS)|"Installation checklist (CMS)"]]. </p>
| |
|
| |
| <li>Update the Online JCL or EXEC:
| |
| <ul>
| |
| <li>Add the DD cards or FILEDEFs for the SIRxxxxx and/or JANxxx files.
| |
|
| |
| <li>Verify that the <var>SYSOPT</var> parameter has the 1 and 2 bits set.
| |
| </ul>
| |
|
| |
| <li>Update CCAIN parameters:
| |
| <ul>
| |
| <li>Increase <var>NFILES</var>, <var>NDCBS</var>, and <var>NDIR</var> for the SIRxxxxx and/or JANxxx files.
| |
|
| |
| <li>Verify that <var>NORQS</var> is at least 5.
| |
| | |
| <li>Verify the online has at least 10 SDAEMON threads (typically defined as IODEV15s).
| |
| </ul>
| |
|
| |
| <li>Start the Online, using an <var>ONLINE</var> load module that contains the
| |
| <var class="product">Sirius Mods</var>.
| |
|
| |
| <li>Open file <var>SIRIUS</var> and execute the following command:
| |
| <p class="code">INCLUDE SETUP.EXE</p>
| |
| <p>
| |
| Follow the instructions on the installation screen (and in the Help
| |
| text for the screen).</p>
| |
|
| |
| <li>Add users to the appropriate SCLASSs for the Sirius APSYs.
| |
|
| |
| <li>Verify success of the installation by compiling each Sirius APSY.
| |
|
| |
| <li>Read
| |
| [[Installing UL/SPF under MVS#UL/SPF server size and additional customization|"UL/SPF server size and additional customization"]]
| |
| to determine if additional APSY-specific customizations are required at your site.
| |
| | |
| <li>Use the [[SirAdmin]] apsy to customize the [[UL/SPF]] environment.
| |
| | |
| </ol>
| |
| | |
| ==Preparing for UL/SPF installation==
| |
| The <var class="product">UL/SPF</var> products are implemented as
| |
| <var class="product">Model 204</var> subsystems.
| |
| The code for all the component subsystems resides in a file called <code>SIRIUS</code> which is typically downloaded from the product section of the website.
| |
|
| |
| ===Obtaining product installation files===
| |
| The files necessary for the installation are available either from
| |
| distribution tapes or from the Sirius web site.
| |
| Downloading and installing from the web site is generally easier, as you don't have to
| |
| wait for tapes to arrive and be cataloged onto your system.
| |
|
| |
| To download product files from the Sirius web site:
| |
| <ol>
| |
| <li>On the Sirius home page, click the "Support" link in the
| |
| "Sirius Home" list in the yellow navigation frame.
| |
| <li>In the "Customer Service" section, click the "Download User Language files" link.
| |
| | |
| This brings you to a Customer Maintenance
| |
| page that contains a list of Sirius Software <var class="product">User Language</var>
| |
| dump files.
| |
| A link on this page provides Help on downloading format, some information about
| |
| different browser behaviors, file sizing information, and more.
| |
| </ol>
| |
| | |
| '''Re-Installing''' <var class="product">UL/SPF</var> typically involves nothing more than downloading and restoring a new version of the <code>SIRIUS</code> file.
| |
| | |
| ===Determining eligible products===
| |
| To download files or maintenance from the Sirius web site, you must have
| |
| a user ID provided by Sirius (contact Technical Support if you need an ID).
| |
| The web site will show only products
| |
| for which your organization is up to date on maintenance or rental payments.
| |
| If a product does not appear on your download page and you believe it should,
| |
| contact Technical Support.
| |
| | |
| If you are working from a distribution tape, files for products
| |
| not purchased by your organization will be present but empty on the installation tape.
| |
|
| |
| Any step of the installation process may be bypassed if it
| |
| applies only to a <var class="product">UL/SPF</var> module you are not
| |
| installing.
| |
|
| |
| ===System requirements===
| |
| <ul>
| |
| <li><var class="product">UL/SPF</var> operates in a <var class="product">Model 204</var> online region, and
| |
| Sirius supports all releases of <var class="product">Model 204</var> that are supported by Rocket / Computer
| |
| Corporation of America.
| |
|
| |
| In the rest of this document, "Online" refers to a region of
| |
| <var class="product">Model 204</var> running an ONLINE load module containing the
| |
| <var class="product">Sirius Mods</var>.
| |
|
| |
| <li>Requirements for server sizes and
| |
| parameter settings for each product are listed in [[Installing UL/SPF under MVS|"UL/SPF server size and additional customization"]].
| |
|
| |
| <li><var class="product">Sirius Mods</var> custom methods and $functions must be activated.
| |
| | |
| The <var class="product">UL/SPF</var> products make extensive use of custom
| |
| $functions that are part of the <var class="product">Sirius Mods</var>.
| |
| Before continuing with installation, follow the instructions in the [[Sirius Mods Installation Guide]]
| |
| to make the $functions active in the target Online.
| |
|
| |
| To test that the <var class="product">Sirius Mods</var> is installed and linked, type
| |
| <code>SIRIUS</code>
| |
| at the <var class="product">Model 204</var> command line to display the status of the
| |
| <var class="product">Sirius Mods</var>.
| |
| An error results if the <var class="product">Sirius Mods</var> is not linked into the
| |
| Online.
| |
| | |
| </ul>
| |
|
| |
| ===User privileges===
| |
| The installing user must have:
| |
| <ul>
| |
| <li>Update access to the JCL or EXECs that bring up the host Online.
| |
|
| |
| <li>The installing user '''must have''' System Manager
| |
| privileges, as well as access to SUBSYSMGMT and the JCL or EXEC that
| |
| runs the Online <var class="product">Model 204</var> region.
| |
| </ul>
| |
|
| |
| ===Full Install or Quick Install===
| |
| | |
| <ul>
| |
| | |
| <li>Sites that have never installed <var class="product">UL/SPF</var> ''must'' use the full
| |
| installation, as there are a number of files to allocate and <var
| |
| class="product">Model 204</var> parameters to update.
| |
| | |
| <li>Sites that are re-installing the latest version of <var class="product">UL/SPF</var>
| |
| may use the quick-install or the full installation (some of whose steps would already be complete,
| |
| such as the allocation and initialization of SIRLOCAL).
| |
| | |
| <li>If you are upgrading from a previous version or maintenance level,
| |
| your site already has a SIRLOCAL file, which holds users' profiles and other local customizations.
| |
| Your existing SIRLOCAL should be left intact and allocated to the Online,
| |
| as the installation process uses SIRLOCAL information to determine which features should be upgraded.
| |
| </ul>
| |
| | |
| ==A "Quick Install" for existing UL/SPF sites==
| |
| If your site hosts a version of <var class="product">UL/SPF</var> earlier than 6.8, you cannot use this "Quick Install guide.
| |
| | |
| You can verify the ULSPF version either in the title of any <var class="product">UL/SPF</var> help screen, or by looking at the content of the <code>VERSION</code> procedure in the <code>SIRIUS</code> file.
| |
|
| |
| Here are the ''Quick Install'' steps:
| |
| | |
| <ol>
| |
| <li>From the "User Language dump files" page in the Support section of the
| |
| Sirius website, download the latest version of the <code>SIRIUS</code> file (which is labeled "All UL/SPF
| |
| products in one file").</li>
| |
| | |
| <li>Verify that the online in which you are installing contains a version of the Sirius Mods at equal to or greater than the <var class="product">UL/SPF</var> version.</li>
| |
| | |
| <li>Restore the <code>SIRIUS</code> file into a 4200-page file on your mainframe.
| |
| The DDNAME for this file in your <var class="product">Model 204</var> regions is
| |
| <code>SIRIUS</code>.
| |
| | |
| If you're upgrading from a previous release, simply overlay your old <code>SIRIUS</code> file.
| |
| | |
| <li>If your site uses the web version of [[SirMon]], there is a change between Version 7.7 and 8.1 to the file that holds historical performance information. You should delete from the <var class="product">SirMon/var> APSY definition the file <code>MONDATA</code>, and add the file <code>SIRSTATS</code>, allocated with at least 5000 pages. In file <code>SIRIUS</code>, run the procedure <code>CREATE.SIRSTATS</code> to define the fields in this file.
| |
| </ol>
| |
| | |
| The <var class="product">UL/SPF</var> APSYs can be set to <code>AUTOSTART</code> if you like. [[SirScan]], [[SirMon]] and [[SirLib]] have SCLASS-sensitive code, so SCLASSes should not be renamed or redefined for these systems.
| |
| | |
| Use the APSY utility SIRADMIN to customize <var class="product">UL/SPF</var> settings.
| |
| | |
| ==Installing UL/SPF under CMS==
| |
| This page gives instructions for installing <var class="product">UL/SPF</var> under CMS,
| |
| including general system and software requirements.
| |
| It assumes you have reviewed [[Preparing for UL/SPF installation]] for details on <var class="product">UL/SPF</var> system requirements.
| |
|
| |
| The <code>SIRIUS</code> Model 204 file, which contains the User Language code that runs [[UL/SPF]], can be obtained from the Support section of the website or from a Sirius distribution tape. If working from a tape, it is shipped with a single tape file in VMFPLC2 DUMP format
| |
| which includes these files:
| |
| <table>
| |
| <tr><th>File name</th>
| |
| <th>Contents</th></tr>
| |
| | |
| <tr><th><i>various</i></th>
| |
| <td>Files required for the installation of <var class="product">Sirius Mods</var>. See the <i>[http://sirius-software.com/maint/download/siri.pdf Sirius Mods Installation Guide]</i> for more details. </td></tr>
| |
| | |
| <tr><th nowrap>ULSPF DUMPSIRI</th>
| |
| <td>A <var class="product">Model 204</var> DUMP of the SIRIUS file that is required for the all subsystems. </td></tr>
| |
| | |
| <tr><th>ULSPF DUMPFIX</th>
| |
| <td>A <var class="product">Model 204</var> DUMP of the SIRFIXES file, (the use of which is now deprecated).
| |
| </td></tr></table>
| |
|
| |
| Installation steps:
| |
| | |
| <ol>
| |
| <li>Install the <var class="product">Sirius Mods</var>.
| |
| <p>
| |
| <var class="product">UL/SPF</var> requires a matching or greater version number of the <var class="product">Sirius Mods</var>.
| |
| For information about installing the <var class="product">Sirius Mods</var>, see the <i>Sirius Mods Installation Guide</i>.</p>
| |
| | |
| <li>Allocate space for the <code>Sirius</code>, and restore it from
| |
| the distribution tape or from the dump files downloaded off the Sirius website.
| |
| <ol type="a">
| |
| <li>Define and format a minidisk to hold the <var class="product">UL/SPF</var> installation files.
| |
| 3400 4096 byte CMS blocks should be sufficient in all cases.
| |
| This requires a 44 cylinder CMS minidisk on a 3390.
| |
|
| |
| <li>Attach a tape drive at virtual address 181 to the owner of the
| |
| installation minidisk defined in step 1.
| |
| Mount the Sirius distribution tape on this tape drive.
| |
|
| |
| <li>Load the files appropriate to your site with the <var>VMFPLC2 LOAD</var> command.
| |
| This can be done most simply with the following sequence of commands:
| |
| <p class="code">TAPE REW
| |
| VMFPLC2 LOAD (EOT
| |
| </p>
| |
|
| |
| <li>Allocate space for the required <var class="product">Model 204</var> datasets. A skeleton exec,
| |
| <var>ULSPFAL</var>, is provided for this purpose.
| |
| Modify this exec to perform the allocations on the appropriate minidisks.
| |
| Allocate space for the following data sets :
| |
| <table>
| |
| <tr><th>SIRIUS
| |
| </th><td>4200 pages (must always be allocated.
| |
| </td></tr>
| |
| <tr><th>SIRLOCAL
| |
| </th><td>1200 pages, must always be allocated.
| |
| </td></tr>
| |
| <tr><th>SIRSTATS or MONDATA
| |
| </th><td>60000 pages, only if you are installing <var class="product">SirMon</var>. Use <code>MONDATA</code> for versions 7.7 and earlier. Use <code>SIRSTATS</code> for versions 8.1 and later.
| |
| </td></tr>
| |
| <tr><th>SIRFILED
| |
| </th><td>1200 pages, only if you are installing <var class="product">SirFile</var>.
| |
| </td></tr>
| |
| <tr><th>SIRLIBD
| |
| </th><td>1200 pages, only if you are installing <var class="product">SirLib</var>.
| |
| </td></tr>
| |
| <tr><th>SIRLIBP
| |
| </th><td>1200 pages, only if you are installing <var class="product">SirLib</var>.
| |
| </td></tr>
| |
| <tr><th>SIRTPROC
| |
| </th><td>2000 pages, only if you are installing <var class="product">SirLib</var>.
| |
| This file can and should be sized much larger if you maintain hundreds or thousands of concurrent change decks in <var class="product">SirLib</var>.
| |
| </td></tr>
| |
| <tr><th>JANCAT
| |
| </th><td>1200 pages, only if you are installing Janus OMNI.
| |
| </td></tr>
| |
| <tr><th>JANSSL
| |
| </th><td>1200 pages, only if you are installing Janus SSL.
| |
| </td></tr></table>
| |
|
| |
| '''IMPORTANT:'''
| |
| <br>
| |
| ''If you are upgrading from a previous
| |
| release'', keep your old copy of <var>SIRLOCAL</var> and any
| |
| application-specific data files, like JANCAT, SIRLIBD, SIRFILED or
| |
| SIRSTATS.
| |
| The installation process uses these files to determine whether to
| |
| perform upgrade actions or new-installation actions.
| |
| | |
| <li>Restore the <code>SIRIUS</code> file with the <var>LOADPROC</var> exec.
| |
| <p>
| |
| To restore, customize the FILEDEF inside the <var>LOADPROC</var> exec to conform to local standards.
| |
| In addition, modify <var>LOADPROC CCAIN</var> to contain a
| |
| valid login ID and password.
| |
| If, for example, you are using the SIRIUS file for the first time,
| |
| make sure it is created, opened, and initialized before the <var>RESTORE</var>. </p>
| |
| <p>
| |
| To run the <var>LOADPROC</var> exec, make sure the Online execs and load modules
| |
| are on an accessed disk, then type the command: </p>
| |
| <p class="code">ONLINE LOADPROC
| |
| </p>
| |
| </ol>
| |
|
| |
| <li>Complete steps 3 through the end in [[Installing UL/SPF under MVS]].
| |
| </ol>
| |
| | |
| ==Installing UL/SPF under MVS==
| |
| ===Overview===
| |
| This section gives instructions for installing <var class="product">UL/SPF</var> under MVS,
| |
| including the general system and software requirements.
| |
| If you received your product on tape, the following instructions apply.
| |
| If like most sites, you download products and updates from the Sirius website,
| |
| see the instructions in [[A "Quick Install" for existing UL/SPF sites]].
| |
| <p>
| |
| '''Note:''' The Sirius
| |
| installation tape for MVS has an internal label of <code>SIRIUS</code>, and it contains
| |
| <var class="product">UL/SPF</var> files in an IEBCOPY unloaded PDS on file 3 of the tape.
| |
| Before continuing, unless you have downloaded the product files from the website,
| |
| ''you must load to disk the unloaded PDS before you can <var>RESTORE</var> the
| |
| individual members to <var class="product">Model 204</var> files.'' </p>
| |
|
| |
| The following JCL will load the <var class="product">UL/SPF</var> files to disk:
| |
| <p class="code">//LOADSIR JOB 0,CLASS=A,MSGCLASS=X,NOTIFY=ME
| |
| //*
| |
| //* Load Sirius products from tape
| |
| //*
| |
| //LIB EXEC PGM=IEBCOPY,REGION=0M
| |
| //T1 DD UNIT=TAPE,LABEL=(1,SL),DSN=SIRIUS.LIB,
| |
| // DISP=(OLD,PASS),VOL=SER=SIRIUS
| |
| //T2 DD UNIT=TAPE,LABEL=(2,SL),DSN=SIRIUS.LOAD,
| |
| // DISP=(OLD,PASS),VOL=SER=SIRIUS
| |
| //T3 DD UNIT=TAPE,LABEL=(3,SL),DSN=SIRIUS.ULSPF,
| |
| // DISP=(OLD,PASS),VOL=SER=SIRIUS
| |
| //*
| |
| //D1 DD DISP=(,CATLG),SPACE=(CYL,(10,0,5),
| |
| // DSN=SIRIUS.LIB,UNIT=SYSDA
| |
| //D2 DD DISP=(,CATLG),SPACE=(CYL,(5,0,2),
| |
| // DSN=SIRIUS.LOAD,UNIT=SYSDA
| |
| //D3 DD DISP=(,CATLG),SPACE=(CYL,(44,0,2),
| |
| // DSN=SIRIUS.ULSPF,UNIT=SYSDA
| |
| //SYSPRINT DD SYSOUT=*
| |
| //SYSIN DD *
| |
| COPY INDD=T1,OUTDD=D1
| |
| COPY INDD=T2,OUTDD=D2
| |
| COPY INDD=T3,OUTDD=D3
| |
| /*
| |
| </p>
| |
|
| |
| The JCL includes references to these files:
| |
| <table>
| |
| <tr><th>File Num / Name
| |
| </th><th>Contents
| |
| </th></tr>
| |
| <tr><th>1 / SIRIUS.LIB
| |
| </th><td>File required for the installation of <var class="product">Sirius Mods</var>. See the <i>[http://sirius-software.com/maint/download/siri.pdf Sirius Mods Installation Guide]</i> for more details.
| |
| </td></tr>
| |
| <tr><th nowrap>3 / SIRIUS.ULSPF(DUMPSIRI)
| |
| </th><td>A <var class="product">Model 204</var> DUMP of the SIRIUS file that is required for all the subsystems.
| |
| </td></tr>
| |
| <tr><th>3 / SIRIUS.ULSPF(DUMPFIX)
| |
| </th><td>A <var class="product">Model 204</var> DUMP of the SIRFIXES file. This file is deprecated and not necessary for this installation.
| |
| </td></tr></table>
| |
|
| |
| ===Installation checklist (MVS)===
| |
| <ol>
| |
| <li>Install the <var class="product">Sirius Mods</var>.
| |
| Refer to the <i>Sirius Mods Installation Guide</i> for details.
| |
| <p>
| |
| '''Note:'''
| |
| The Online in
| |
| which <var class="product">UL/SPF</var> will run must point to a load module containing the <var class="product">Sirius Mods</var>.
| |
| Also, as of version 6.8, <var class="product">UL/SPF</var> releases
| |
| require a matching or greater version number of the <var class="product">Sirius Mods</var>. </p>
| |
|
| |
| <li>Allocate the space required for the Sirius files. Note that the SIRIUS file has X'0221' privileges, which does ''not'' allow <var>RESTORE</var>. If you are creating a new SIRIUS file from scratch, this will not be a problem. But if you are restoring into your existing SIRIUS file, you will have to <var>CREATE</var> the file first (to wipe out existing content) before you execute the <var>RESTORE</var>. The command sequence would be something like:
| |
| <p class="code">CREATE FILE SIRIUS
| |
| END CREATE
| |
| OPEN FILE SIRIUS
| |
| IN SIRIUS RESTORE 192 FROM <whatever>
| |
| </p>
| |
| | |
| <table>
| |
| <tr><th>SIRIUS</th>
| |
| <td>4200 pages; must always be allocated.</td></tr>
| |
| | |
| <tr><th>SIRLOCAL
| |
| </th><td>1200 pages; must always be allocated.</td></tr>
| |
| | |
| <tr><th nowrap>SIRSTATS or MONDATA
| |
| </th><td>4000 pages; only if you are installing <var class="product">SirMon</var>. Use MONDATA for versions 7.7 and earlier. Use SIRSTATS for versions 8.1 and later.</td></tr>
| |
| | |
| <tr><th>SIRFILED</th>
| |
| <td>1200 pages; only if you are installing <var class="product">SirFile</var>.</td></tr>
| |
| | |
| <tr><th>SIRLIBD</th>
| |
| <td>1200 pages; only if you are installing <var class="product">SirLib</var>.</td></tr>
| |
| | |
| <tr><th>SIRLIBP</th>
| |
| <td>1200 pages; only if you are installing <var class="product">SirLib</var>.</td></tr>
| |
| | |
| <tr><th>SIRTPROC</th>
| |
| <td>2000 pages; only if you are installing <var class="product">SirLib</var>.
| |
| This file can and should be sized much larger if you maintain hundreds or thousands of concurrent change decks in <var class="product">SirLib</var>.</td></tr>
| |
| | |
| <tr><th>JANCAT</th>
| |
| <td>1200 pages; only if you are installing Janus OMNI.</td></tr>
| |
| | |
| <tr><th>JANSSL</th>
| |
| <td>1200 pages; only if you are installing Janus SSL.</td></tr>
| |
| </table>
| |
|
| |
| <p>
| |
| '''IMPORTANT:'''
| |
| <br>
| |
| ''If you are upgrading from a previous release'', keep your old copies of SIRLOCAL and any
| |
| application-specific data files, like JANCAT, SIRLIBD, SIRFILED, or SIRSTATS.
| |
| The installation process uses these files to determine whether to
| |
| perform upgrade actions or new-installation actions. </p>
| |
| | |
| Restore SIRIUS, noting the following:
| |
| <ul>
| |
| <li>Modify LOADPROC in the JCL library created during the $functions
| |
| installation (usually <code>SIRIUS.V<i>xxx</i>.LIB</code>, where <var class="term">xxx</var>
| |
| is a version number) to refer to an appropriate load module and CCA<i>xxxxx</i> files.
| |
| Note that LOADPROC may have been customized for your site to include only those files relevant to your
| |
| installation process.
| |
|
| |
| <li>Rename database DSNs to conform to local standards.
| |
|
| |
| <li>Provide a valid logon ID and password for the CCAIN stream for this job.
| |
| If, for example, you are using the SIRIUS file for the first time,
| |
| make sure it is created, opened, and initialized before the <var>RESTORE</var>.
| |
| </ul>
| |
|
| |
| <li>Update the Online JCL or EXEC:
| |
| <ol type="a">
| |
| <li>Add DD (MVS) cards or FILEDEFs (CMS) for the Sirius files.
| |
| The following list identifies the files for which DD cards or FILEDEFs may be needed:
| |
| <table>
| |
| <tr><th>SIRIUS
| |
| </th><td>must always be allocated
| |
| </td></tr>
| |
| <tr><th>SIRLOCAL
| |
| </th><td>must always be allocated
| |
| </td></tr>
| |
| <tr><th>SIRSTATS or MONDATA
| |
| </th><td>if installing <var class="product">SirMon</var> and using the web interface. Use MONDATA for UL/SPF versions 7.7 and prior. Use SIRSTATS for UL/SPF versions 8.1 and later.
| |
| </td></tr>
| |
| <tr><th>SIRFILED
| |
| </th><td>if installing <var class="product">SirFile</var>
| |
| </td></tr>
| |
| <tr><th nowrap>SIRLIBD, SIRLIBP, SIRTPROC
| |
| </th><td>if installing <var class="product">SirLib</var>
| |
| </td></tr>
| |
| <tr><th>JANCAT
| |
| </th><td>if installing JANUS OMNI Access Module
| |
| </td></tr>
| |
| <tr><th>JANSSL
| |
| </th><td>if installing JANUS SSL Module
| |
| </td></tr></table>
| |
| | |
| <li>Verify that the Online environment allows the use of file groups and APSY subsystems.
| |
| <ul>
| |
| <li>To use permanent file groups, the Online must have allocated an
| |
| initialized CCAGRP file, and the SYSOPT parameter must contain the <code>2</code> bit.
| |
| | |
| <li>To use APSYs, an Online must have allocated an initialized CCASYS file
| |
| (with all fields defined), and the SYSOPT parameter
| |
| must contain the <code>1</code> bit.
| |
| </ul>
| |
| For more information about APSYs and file groups, see the <i>[http://www.rocketsoftware.com/m204/products/index/documentation/v7r4/M204-System-Mgr/view Rocket Model 204 System Manager's Guide]</i>.</ol>
| |
| | |
| <li>Verify the online has a minimum of 10 [[Sdaemons|Sdaemon]] threads allocated. These threads are typically defined as IODEV15s.
| |
| | |
| <li>Modify the User 0 stream.
| |
|
| |
| Adjust these parameters:
| |
| <table>
| |
| <tr><th>NFILES
| |
| </th><td>Increase by the number of <var class="product">UL/SPF</var> files.</td></tr>
| |
| <tr><th>NDCBS
| |
| </th><td>Increase by the number of <var class="product">UL/SPF</var> files.</td></tr>
| |
| <tr><th>NDIR
| |
| </th><td>Increase by the number of <var class="product">UL/SPF</var> files.</td></tr>
| |
| <tr><th>NORQS
| |
| </th><td>Verify setting is at least 5.</td></tr>
| |
| </table>
| |
|
| |
| <li>Start the <var class="product">Model 204</var> Online region, verifying that it points
| |
| to a load module containing the <var class="product">Sirius Mods</var>.
| |
| | |
| <li>Issue <code>OPEN FILE SIRIUS</code> (no password is required), and execute the following command:
| |
| <p class="code">INCLUDE SETUP.EXE
| |
| </p>
| |
|
| |
| This procedure performs all installation functions for new users, and all upgrade functions for reinstalling users.
| |
| No user profiles or other site-specific customization will be lost.
| |
| If any problems are encountered while running this procedure, correct the problem and re-execute.
| |
|
| |
| The procedure SETUP.EXE also builds an APSY subsystem called <code>SETUP.EXE</code>.
| |
| If installations need to be re-run, the subsystem may be invoked
| |
| rather than the procedure.
| |
| | |
| During APSY execution, some error messages are not suppressed to aid in diagnosing any installation problems.
| |
| For example, you will be able to see if an installation failed because
| |
| a file was enqueued in a different Online, etc.
| |
|
| |
| <li>Add users to the appropriate SCLASSes for any private or semi-public Sirius APSYs.
| |
|
| |
| The installing user is automatically added to the administration SCLASS in all Sirius APSYs.
| |
|
| |
| <li>Verify the installation of the subsystem(s) by compiling all of the subsystems.
| |
| <table>
| |
| <tr><th>Enter ...
| |
| </th><th>To test the ...
| |
| </th></tr>
| |
| <tr><th>SIRSCAN START
| |
| </th><td>Journal scanner
| |
| </td></tr>
| |
| <tr><th>SIRFILE START
| |
| </th><td>File Monitoring subsystem
| |
| </td></tr>
| |
| <tr><th>SIRPRO START
| |
| </th><td>Developers' Environment
| |
| </td></tr>
| |
| <tr><th>SIRMON START
| |
| </th><td>Online performance monitor
| |
| </td></tr>
| |
| <tr><th>SIRLIB START
| |
| </th><td>Change Management system
| |
| </td></tr>
| |
| <tr><th>JANCAT START
| |
| </th><td>Janus OMNI Table manager
| |
| </td></tr>
| |
| <tr><th>JANSSL START
| |
| </th><td>Janus SSL certificate management system
| |
| </td></tr></table>
| |
|
| |
| If any of these subsystems fails to compile, ensure that the subsystem
| |
| is STOPped, and run it under <code>TEST DEBUG</code> mode.
| |
| For example, to determine why SIRSCAN failed to compile, enter:
| |
| <p class="code">TEST DEBUG SIRSCAN
| |
| </p>
| |
|
| |
| <li>This step is optional.
| |
| Modify the online input stream so User 0 initializes (compiles) the <var class="product">UL/SPF</var>
| |
| subsystems.
| |
| Do this by placing one or more of the following in User 0's input stream:
| |
| <p class="code">SIRSCAN START
| |
| SIRFILE START
| |
| SIRPRO START
| |
| SIRMON START
| |
| SIRLIB START
| |
| JANMAN START
| |
| JANCAT START
| |
| START SUBSYSTEM ULSPF
| |
| </p>
| |
| This ensures that the subsystems are started for non-administrative
| |
| users, and it shifts the overhead of compilation to a non-peak
| |
| computing period.
| |
|
| |
| <li>Review
| |
| [[#UL/SPF server size and additional customization|"UL/SPF server size and additional customization"]]
| |
| for specific requirements of individual APSY components of <var class="product">UL/SPF</var>.
| |
| </ol>
| |
| <p>
| |
| '''Note:'''
| |
| CCATEMP usage may increase with <var class="product">UL/SPF</var>.
| |
| CCATEMP should be monitored (<code>VIEW TEMPSIZE</code>, <code>VIEW TEMPMAX</code>) to ensure that
| |
| sufficient space is allocated to accommodate the additional activity. </p>
| |
| | |
| ===UL/SPF server size and additional customization===
| |
| The minimum <var class="product">UL/SPF</var> server size requirements are listed below.
| |
| The actual server size requirements may vary slightly, because of table
| |
| settings in the local Online <var class="product">Model 204</var> regions, and because of slight
| |
| differences between UTABLE requirements in different versions of
| |
| <var class="product">Model 204</var>.
| |
| <table>
| |
| <tr><th>Subsystem name
| |
| </th><th>Minimum server
| |
| </th></tr>
| |
| <tr><th>SIRSCAN
| |
| </th><td>180K
| |
| </td></tr>
| |
| <tr><th>SIRDBA
| |
| </th><td>180K
| |
| </td></tr>
| |
| <tr><th>SIRFILE
| |
| </th><td>230K
| |
| </td></tr>
| |
| <tr><th>SIRPRO
| |
| </th><td>220K
| |
| </td></tr>
| |
| <tr><th>SIRLIB
| |
| </th><td>135K
| |
| </td></tr>
| |
| <tr><th>SIRADMIN
| |
| </th><td>150K
| |
| </td></tr>
| |
| <tr><th>SIRMON
| |
| </th><td>120K
| |
| </td></tr>
| |
| <tr><th>ULSPF
| |
| </th><td>135K
| |
| </td></tr></table>
| |
|
| |
| ===UTABLE settings===
| |
| As of <var class="product">UL/SPF</var> version 8.1 (June 2013), all <var class="product">UL/SPF</var> subsystems can be set to bypass UTABLE resets. Use the SIRADMIN subsystem to set this feature.
| |
| For versions prior to 8.1, and for those who choose to leave the UTABLE resets in place, <var class="product">UL/SPF</var> will capture local UTABLE settings before they reset them to those required by <var class="product">UL/SPF</var>.
| |
|
| |
| Initial problems with <var class="product">UL/SPF</var> subsystems are usually associated with one
| |
| or two extremely small default UTABLE settings.
| |
| Running the failing apsy in TEST DEBUG mode will highlight UTABLE parameters that need to be increased.
| |
|
| |
| ===Additional setup for SirLib===
| |
| Read and follow the instructions in the appendix "Getting
| |
| Started" in the <i>[http://sirius-software.com/maint/download/libr.pdf SirLib User's Guide]</i>.
| |
|
| |
| ===Additional setup for SirScan===
| |
| | |
| The <var class="product">SirScan</var> administrator may use SIRADMIN option 4 to set default I/O
| |
| and record maximums for users in the various <var class="product">SirScan</var> SCLASSes.
| |
| This is described at the beginning of the
| |
| <i>[http://sirius-software.com/maint/download/scanr.pdf SirScan User's Guide]</i>.
| |
|
| |
| ===Additional setup for SirMon===
| |
| When users are added to SCLASSes, note that there is a special <var>BUMP</var> SCLASS.
| |
| Any user added to this SCLASS gains the ability to <var>BUMP</var> other users.
| |
| This class does not provide access to customizing options in <var class="product">SirMon</var>.
| |
| Only users in the ADMIN SCLASS are able to add custom screen definitions to <var class="product">SirMon</var>.
| |
|
| |
| If the <var class="product">SirMon</var> background monitor is to be used,
| |
| add the following line to User 0's input stream:
| |
| <p class="code">SIRMON BACKGROUND
| |
| </p>
| |
| The Background monitor may also be started automatically in a BATCH2 thread or an sdaemon thread.
| |
| Consult the <i>[http://sirius-software.com/maint/download/libr.pdf SirMon User's Guide]</i>
| |
| for details.
| |
|
| |
| You can customize statistic thresholds or use the Sirius-supplied defaults
| |
| to establish problem conditions.
| |
|
| |
| As of <var class="product">UL/SPF</var> Version 6.8, <var class="product">SirMon</var> has a feature to send warnings to
| |
| e-mail addresses and cell phones (via e-mail).
| |
| This feature requires <var class="product">Janus Sockets</var> and a started <var class="product">Janus Sockets</var> port.
| |
|
| |
| ===Additional setup for SirFile===
| |
| If the <var class="product">SirFile</var> background monitor is to be used, add the following line
| |
| to User 0's input stream:
| |
| <p class="code">SIRFILE BACKGROUND
| |
| </p>
| |
| As with <var class="product">SirMon</var>, the Background monitor may be started automatically in a BATCH2 thread or in an
| |
| sdaemon thread, and you can consult the
| |
| <i>[http://sirius-software.com/maint/download/filr.pdf SirFile User's Guide]</i> for details.
| |
|
| |
| You can customize the system and file-specific thresholds or use the
| |
| Sirius-supplied defaults to establish problem conditions.
| |
| | |
| ===UL/SPF access privileges and SCLASSes===
| |
| Each component application of <var class="product">UL/SPF</var> has its own APSY definition and
| |
| privileges associated with SCLASSes.
| |
| If you have a good reason for doing so, you can redefine any of the <var class="product">UL/SPF</var> APSYs as <code>PUBLIC</code>,
| |
| <code>SEMI-PUBLIC</code>, or <code>PRIVATE</code>.
| |
| Consult Sirius Software if you are unsure of the effect of a proposed change.
| |
| | |
| ==UL/SPF on the Web==
| |
| Web-specific versions of the <var class="product">UL/SPF</var> subsystems are actively being developed and supported, and they are available to sites that own <var class="product">[[Janus Web Server]]</var>.
| |
| | |
| All the <var class="product">UL/SPF</var> APSYs can be used on the web via <var class="product">Janus Web Legacy Support</var>, which simply translates the 3270 screens of the underlying product into HTML. Web-specific versions of both <var class="product">[[SirScan]]</var> and <var class="product">[[SirMon]]</var> can be invoked by setting up some <var class="product">Janus Web Server</var> web rules.
| |
| | |
| ===Setup for web-based SirScan===
| |
| Web-based <var class="product">SirScan</var> is very lightweight, and requires a minimum of web rules to run.
| |
| | |
| <ol>
| |
| <li>Define a <var class="product">Janus Web Server</var> port.
| |
| | |
| <li>Define the following rule to invoke <var class="product">SirScan</var>:
| |
| | |
| <p class="code">JANUS WEB <var class="term">portname</var> ON /SIRSCAN/* CMD 'SIRSCAN *'
| |
| </p>
| |
| | |
| <li>The above rule will make <var class="product">SirScan</var> available, but it will not necessarily require a logon to the system, so you will need to add rules to force users to log in as well:
| |
| | |
| <p class="code">JANUS WEB <var class="term">portname</var> DISALLOW /SIRSCAN/*
| |
| JANUS WEB <var class="term">portname</var> ALLOW /SIRSCAN/* USER *
| |
| </p>
| |
| | |
| <li>Because the above rules force users to login, the port on which <var class="product">SirScan</var> runs should either:
| |
| <ul>
| |
| <li>Be only on a company intranet.
| |
| <li>Be SSL protected, to prevent userids and passwords from being sent over the internet in clear text format.
| |
| </ul>
| |
| | |
| The above rules will work on an unprotected port, but it is '''very strongly recommended''' that this feature only be used when SSL protection is in effect.
| |
| </ol>
| |
| | |
| ===Setup for web-based SirMon===
| |
| This applies only to <var class="product">UL/SPF</var> Version 8.1 and later.
| |
| | |
| Because web-based <var class="product">SirMon</var> employs XML, XSLT, Javascript, a stylesheet and some graphics,
| |
| the web rules needed to run <var class="product">SirMon</var> on the web are a little more complex.
| |
| | |
| <ol>
| |
| <li>Define a <var class="product">Janus Web Server</var> port.
| |
| | |
| <li>Define the following rules to invoke <var class="product">SirMon</var>:
| |
| | |
| <p class="code">JANUS WEB <var class="term">portname</var> TYPE ANY *.PNG IMAGE/PNG
| |
| JANUS WEB <var class="term">portname</var> TYPE ANY *.CSS TEXT/CSS
| |
| JANUS WEB <var class="term">portname</var> TYPE ANY *.JS APPLICATION/X-JAVASCRIPT
| |
| JANUS WEB <var class="term">portname</var> ON /*.CSS OPEN SIRIUS SEND *.CSS
| |
| JANUS WEB <var class="term">portname</var> ON /SIRMON/* CMD SIRMON
| |
| JANUS WEB <var class="term">portname</var> ON /SIRMON/*.GIF OPEN SIRIUS SEND *.GIF EXPIRE +2147483
| |
| JANUS WEB <var class="term">portname</var> ON /SIRMON/*.PNG OPEN SIRIUS SEND *.PNG EXPIRE +2147483
| |
| JANUS WEB <var class="term">portname</var> ON /SIRMON/*.JS OPEN SIRIUS SEND *.JS BINARY EXPIRE +2147483
| |
| JANUS WEB <var class="term">portname</var> ON /AJAX/* OPEN SIRIUS SEND *
| |
| JANUS WEB <var class="term">portname</var> ON /AJAX/*.JS OPEN SIRIUS SEND *.JS TEXT
| |
| JANUS WEB <var class="term">portname</var> ON /AJAX/*.UL OPEN SIRIUS CMD 'INCLUDE *.UL'
| |
| JANUS WEB <var class="term">portname</var> DISALLOW /SIRMON/*
| |
| JANUS WEB <var class="term">portname</var> ALLOW /SIRMON/* USER *
| |
| JANUS WEB <var class="term">portname</var> TYPE ANY *.XML TEXT/XML
| |
| JANUS WEB <var class="term">portname</var> TYPE ANY *.XSL TEXT/XSL
| |
| JANUS WEB <var class="term">portname</var> ON /SIRMON/*.XSL OPEN SIRIUS SEND *.XSL EXPIRE +2147483
| |
| JANUS WEB <var class="term">portname</var> ON /SIRMON/*.CSS OPEN SIRIUS SEND *.CSS EXPIRE +2147483
| |
| JANUS WEB <var class="term">portname</var> ON /SIRMON/TEXTJS/*.JS OPEN SIRIUS SEND *.JS TEXT EXPIRE +2147483
| |
| JANUS WEB <var class="term">portname</var> ON /SIRMON/BUILDJS/*.JS CMD SIRMON
| |
| | |
| OPEN SIRSTATS
| |
| IN SIRSTATS INITIALIZE KEEPDEFS
| |
| </p>
| |
| | |
| <li>The above rules will make <var class="product">SirMon</var> available, but they will not necessarily require a logon to the system, so you will need to add rules to force users to log in as well:
| |
| | |
| <p class="code">JANUS WEB <var class="term">portname</var> DISALLOW /SIRMON/*
| |
| JANUS WEB <var class="term">portname</var> ALLOW /SIRMON/* USER *
| |
| </p>
| |
| | |
| <li>Because the above rules force users to login, the port on which <var class="product">SirMon</var> runs should either:
| |
| <ul>
| |
| <li>Be only on a company intranet.
| |
| | |
| <li>Be SSL protected, to prevent userids and passwords from being sent over the internet in clear text format.
| |
| </ul>
| |
| | |
| The above rules will work on an unprotected port, but it is '''very strongly recommended''' that this feature only be used when SSL protection is in effect.
| |
| | |
| '''Note:''' Using <var class="product">SirMon</var> on the web also requires the '''SIRSTATS''' file. As shown in the above web rules, SIRSTATS can be re-initialized each time the Online comes up. SIRSTATS contains historical snapshots of system performance, and the file will fill up if not archived or re-initialized on occasion.
| |
| </ol>
| |