Migrate the PPT and PCT tables using RDO, if desired.<br />17.<br />Cycle CICS and test that MAGEC comes up by entering the trans-id of TS01. You should receive the logon screen. You may (cont.)<br />log onto MAGEC using the employee number of |*call tech support for number*| and a password of |*call tech support for (cont.)<br />password*|. Pressing PF15 at any time exits MAGEC completely, returning to CICS.<br />18.<br />If you wish to use the MAGEC TP Spooler, you must initialize the two spooler files, the RPHK1 file and the SPLK1 file. (cont.)<br />To do this you must execute the RPHINIT and SPLINIT jobstreams. Refer to exhibit 1.2.2.a. The files must be closed to (cont.)<br />CICS when these are run.<br /># <br />z/OS Upgrade<br />The upgrade will take 1-3 hours, normally. You should schedule to do it while all the MAGEC files are closed to CICS (cont.)<br />and to any other region. The components required to upgrade your MAGEC system include:<br />1.<br />MAGEC.BACKUP tape containing IEBCOPY of complete MAGEC Load library.<br />2.<br />MAGEC.DATABASE tape containing upgraded "source" and dictionary data for MAGEC.<br />3.<br />New documentation manuals.<br />The steps to do in order to apply the upgrade are:<br />A.<br />**Back Up** your MAGEC dictionary files and libraries!!!<br />B.<br />Use IEBCOPY to restore the MAGEC.BACKUP tape to the MAGEC loadlibrary.<br />**(BLKSIZE = 23,476 , size approximately 10 cylinders). If you wish to load into a library with a blocksize other than 23,476 you must use the COPYMOD option of IEBCOPY, instead of the COPY option.<br />C.<br />If you currently have MAGEC 2.x installed and are upgrading to MAGEC 3.x, refer to Appendix A.<br />D.<br />Execute the ALALDFIL program (from new library) using the MAGEC.DATABASE tape as input. The JCL should be on your (cont.)<br />online editor file named: ALALDEX. The MAGEC.DATABASE tape is UNLABELED. You should run this while your online system (cont.)<br />is down** to avoid potential problems, it should run from one hour to three hours in duration. You may wish to run (cont.)<br />MAGECLBR with a -MAGECIDX FCD control card before running ALALDFIL if you have modified any of the FCD (Security) (cont.)<br />profiles for MAGEC system functions.<br />E.<br />Modify your PPT entries as required. The new version of MAGEC has several new online programs which were not in the (cont.)<br />earlier releases. You can use MAGECLBR to punch off the member named DFHPPT, if you wish. It contains all the entries (cont.)<br />needed for MAGEC plus dummy entries for future expansion. Refer to the Offline Utilities chapter of your ** (cont.)<br />Programmer's Reference Guide** for a detailed discussion of MAGECLBR. The control card to punch DFHPPT (cont.)<br />is:<br />-MAGECPCH LIB DFHPPT<br />&nbsp;<br />**<br />NOTE:<br />**<br />Be sure that your concatenation of loadlibraries includes the **largest blocksize library first**. z/OS allocates space (cont.)<br />to read blocks into based upon the size of the first file in your concatenation. Unlike with data files, z/OS will not (cont.)<br />issue a warning or error message when CICS loads a program from a library which has a blocksize larger than the (cont.)<br />allocated space"it will merely truncate the portion from each library block which does not fit in the space, leaving (cont.)<br />gaps of unexecutable binary zeros in the middle of the program. The abends are difficult to debug, so it is wise to (cont.)<br />check your concatenation before using it. If you cannot, or do not desire to, place the largest library first in the (cont.)<br />concatenation, you can specify a DCB with a BLKSIZE set to the largest of all the concatenated libraries. The DCB (cont.)<br />should be on the first DD statement.<br />**RECOMMENDATION:** If your installation wishes to use a separate "**test loadlibrary**" for newly modified programs (cont.)<br />(**we recommend this**), it must be concatenated *before* the "production" loadlibrary. This will allow you to make a (cont.)<br />change to a program and catalogue it to the test library, which CICS will search first. It will find the new version in (cont.)<br />the test library, and not try to find the older program in the production library. In the event you decide your new (cont.)<br />version is NOT working properly, just deleting it from the test library will cause CICS to get the older version (cont.)<br />instead of the flawed new version. You should do the CEMT NEWCOPY (or PHASEIN) command or restart CICS to be sure the (cont.)<br />unwanted copy is not held in cache!**Once you are sure the new version is good, move it to the production (cont.)<br />loadlibrary.<br />Please call MAGEC Support at (214) 202-4965 if you have any problems.<br /># <br />VSE Initial Installation<br />The MAGEC system is normally installed initially by one of MAGEC Software's technical representatives, this topic is (cont.)<br />provided to enable you (in the event it becomes necessary) to install MAGEC without having such a technician available, (cont.)<br />and to help you to prepare for what will be done when the installation commences. You should read the Mainframe (cont.)<br />Pre-Installation topic before this topic. The components required to initially install your MAGEC system (cont.)<br />include:<br />1.<br />MAGEC.BACKUP tape containing VSE library backup of complete MAGEC PHASE and OBJECT library.<br />2.<br />MAGEC.DATABASE tape containing upgraded "source" and dictionary data for MAGEC.<br />3.<br />Documentation manuals.<br />NOTE:<br />**<br />If MAGEC is already installed on your computer you should probably not be reading this topic, you should be reading the ** VSE Upgrade** topic.<br />**<br />NOTE:<br />**<br />The exhibits (in the back of this booklet) referenced in these instructions are extracted from a larger internal (cont.)<br />manual, which accounts for the seemingly strange exhibit numbers. Using the same exhibit numbers in both manuals is an (cont.)<br />advantage in the event that we need to render telephone assistance to you.<br />The steps to do in order to install MAGEC are:<br />1.<br />Create a 20,000 block VSE library, with sufficient space for approximately 100 members.<br />2.<br />Load the library using LIBR with the MAGEC.BACKUP tape as input. The tape is in "old" VSE format with IJSYSRL and IJSYSCL files (may be named MAGECRL and MAGECCL) included.<br />3.<br />Create the JCL named "ALGTPCHX" (see exhibit 1.1.5.1). Be sure to set the LIBDEF pointing to the newly created loadlibrary.<br />4.<br />Execute ALGTPCHX using the control cards (see exhibit 1.1.5.2.a), the output file (SYS005) should require about 20 (cont.)<br />tracks (or less). It will be a sequential file containing "bootstrap" members to eliminate the need for you to do much (cont.)<br />typing for the file definitions and CICS table entries.<br />5.<br />Use ICCF (or another editor) to separate the punched members (from SYS005, above). There will be a separator card (cont.)<br />indicating the name of each member. The separator cards start with -MAGECREP LIB (beginning in column 1). Save the (cont.)<br />individual split-out members in a PDS or other online librarian file for later use, use the 8-character name which is (cont.)<br />specified in the separator cards immediately following "-MAGECREP LIB ".<br />6.<br />Modify the IDCAMS control cards (member name: DEFFILES) to suit your environment. At minimum you must provide the (cont.)<br />VOLUME name. It is permissible to alter CI sizes, change the REUSE to SPEED, or make other desired (cont.)<br />changes.<br />7.<br />Execute IDCAMS using the DELETE/DEFINE control cards from above. Highest return code should be 8 (the DELETE commands (cont.)<br />should get a not found" the first time you run this). The SPL file (MAGEC-SPL-CLUSTER) is rather large (approx 775 (cont.)<br />tracks). The total space requirement for all files, including the SPL and RPH files, will be almost 200 cylinders for (cont.)<br />3380 drives.<br />8.<br />Create ALANULEX JCL (see exhibit 1.2.2), be sure to include the DD statements (see exhibit 1.1.6.2.2) for all the MAGEC (cont.)<br />files, also set the LIBDEF pointing to the new library. The DLBL statements are in the member named VSAMDLBL from step (cont.)<br />5.<br />9.<br />Execute ALANULEX. This job initializes all the files. It runs for 30-45 minutes or longer since it populates the (cont.)<br />spooler files as well. The print ourput will show the VSAM file statuses for the files.<br />10.<br />Execute ALGTPCHX (from step 3) once more, this time with only one control card (see exhibit 1.1.5.2.c). The output will contain a host of sample jobstreams for various MAGEC batch processes.<br />11.<br />Create ALALDEX JCL (see exhibit 2.3). Include the DLBL statements and LIBDEF.<br />12.<br />Execute ALALDEX. This job reads the MAGEC.DATABASE tape (SYS010) and populates the MAGEC VSAM files. It will run approximately 1-2 hours, depending on contention with other regions, etc.<br />13.<br />While step 12 is running, use ICCF (or another editor) to separate and tailor the jobstreams. They will have separator cards preceding each member, as before.<br />14.<br />Assemble the PCT, FCT, and PPT tables using the DFHPCT, DFHFCT, and DFHPPT members created in step 5.<br />15.<br />Add the DLBL statements (VSAMDLBL) to your CICS startup deck, add the MAGEC library to the DFHRPL DLBL. Refer to exhibit 1.1.6.2.2.<br />16.<br />Migrate the PPT and PCT tables using RDO, if desired.<br />17.<br />Cycle CICS and test that MAGEC comes up by entering the trans-id of "TS01". You should receive the logon screen. You (cont.)<br />may log onto MAGEC using the employee number of |*call tech support for number*| and a password of |*call tech support (cont.)<br />for password*|. Pressing PF15 at any time exits MAGEC completely, returning to CICS.<br />18.<br />If you wish to use the MAGEC TP Spooler, you must initialize the two spooler files, the RPHK1 file and the SPLK1 file. (cont.)<br />To do this you must execute the RPHINIT and SPLINIT jobstreams. Refer to exhibit 1.2.2.a. The files must be closed to (cont.)<br />CICS when these are run.<br /># <br />VSE Upgrade<br />The components required to upgrade your MAGEC system include:<br />1.<br />MAGEC.BACKUP tape containing VSE format backup of complete MAGEC core-image, and relocatable libraries.<br />2.<br />MAGEC.DATABASE tape containing upgraded "source" and dictionary data for MAGEC.<br />3.<br />New documentation manuals.<br />The steps to do in order to apply the upgrade are:<br />A.<br />**Back Up** your MAGEC dictionary files and libraries!!!<br />B.<br />For VSE/SP, use LIBR to restore the MAGEC.BACKUP tape to the MAGEC library. (OLDLIB=IJSYSCL and OLDLIB=IJSYSRL). For VSE (pre-SP) use the RESTORE utility.<br />C.<br />Execute the ALALDFIL program (from new library) using the MAGEC.DATABASE tape as input. The JCL should be on your online editor file named: ALALDEX.<br />You may wish to run MAGECLBR with a -MAGECIDX FCD control card before running ALALDFIL if you have modified any of the FCD (Security) profiles for MAGEC system functions.<br />The MAGEC.DATABASE tape is UNLABELED. You should run this while your online system is **down** to avoid potential problems, it should run from one hour to three hours in duration.<br />D.<br />Modify your PPT entries as required. The new version of MAGEC has several new online programs which were not in the (cont.)<br />earlier releases. It has been the standard of MAGEC Software to populate the PPT table with dummy entries to (cont.)<br />accommodate adding new modules from time to time. Some users choose to delete these unused, disabled PPT entries in (cont.)<br />order to clean up their tables. This means that you might need to add a few new entries. The I/O modules (MMP653, and (cont.)<br />MMP698) have been re-written in Command-Level Cobol (as of version 2.1); the control programs (MMP670 and MMP699) have (cont.)<br />also been re-written in Cobol (as of version 2.4); this requires a different PPT definition from earlier versions. You (cont.)<br />can use MAGECLBR to punch off the member named DFHPPT, if you wish. It contains all the entries needed for MAGEC plus (cont.)<br />dummy entries for future expansion. Refer to the Offline Utilities chapter of your ** Programmer's Reference Guide** (cont.)<br />for a detailed discussion of MAGECLBR. The control card to punch DFHPPT is:<br />-MAGECPCH LIB DFHPPT<br />&nbsp;<br />Please call MAGEC Support at (214) 202-4965 if you have any problems.<br /># <br />PC-MAGEC Installation - Realia<br />MAGEC no longer supports the Realia COBOL compiler. Ask us about MAGEC for the [ LAMP Stack!](https://magec.com/images/MAGEC_RAD_PHP.pdf)<br /># <br />PC-MAGEC Installation - Micro Focus Cobol<br />MAGEC no longer supports the Micro Focus COBOL compiler. Ask us about MAGEC for the [LAMP Stack!](https://magec.com/images/MAGEC_RAD_PHP.pdf)<br />**Obsolete documentation left here for reference:** <br />After completing the installation your system should contain the following directories for MAGEC.<br />\MAGMF<br />&nbsp;<br />\MAGMF\JCL<br />&nbsp;<br />MAGEC needs approximately 20Mbytes of hard disk space. It will run on 286, 386, or 486, or Pentiuim machines with at (cont.)<br />least 640Kbytes of memory plus 2Mbytes extended memory (8Mbytes minimum recommended if using (cont.)<br />Windows.<br />There are two installations you must accomplish, first for the Server, second for the Workstation. MicroFocus (cont.)<br />Professional Cobol (v3.2 or later) should be installed prior to installing MAGEC since it adds statements to your (cont.)<br />CONFIG.SYS and/or AUTOEXEC.BAT which MAGEC's installation searches for and modifies. If installing the Windows, or GUI (cont.)<br />Windows versions the installation will create a Windows group and icons for you.<br />**<br />NOTE:<br />**<br />The procedures below assume that your removable disk unit is drive A: - if it is another drive then you should adjust (cont.)<br />the command accordingly. Likewise, they assume that your \MAGMF directory is on your C: drive, if not, adjust (cont.)<br />accordingly. The \COBOL directory is Micro Focus Professional COBOL. From the DOS prompt, or (for Windows installation) (cont.)<br />from Windows File / Run, execute:<br />a: \INSTALIT<br />&nbsp;<br />If you did not choose to allow the install program to modify your AUTOEXEC.BAT and CONFIG.SYS files you should also add the MAGMF and Cobol directories to your PATH or MAP):<br />&nbsp;c:\MAGMF\JCL;\COBOL\EXEDLL<br />&nbsp;<br />And, you should include the following settings for environment variables.<br /><br />next: install03.md.txt