---<br />title: "install_main"<br />original_file: "install_main"<br />generated: "2026-06-12 10:24:21"<br />---<br /><br />**<br /># <br />Installation Guide<br />## <br />Resource Requirements<br />Before the MAGEC installer arrives to install MAGEC on your mainframe** computer, there are several things that can be (cont.)<br />done to help ensure a problem-free installation. The most important of these things is to allocate the needed (cont.)<br />resources.<br />## <br />Library<br />One of the first steps in installing MAGEC will be to create and load an executable library. In the z/OS environment (cont.)<br />you will use whatever facility you normally use (i.e. ISPF) to create the library with a BLKSIZE=23,476, then use (cont.)<br />IEBCOPY to load it from the MAGEC.BACKUP tape. In a VSE environment, you will use RESTORE or LIBR to create and load (cont.)<br />the library.<br />**<br />NOTE:<br />**<br />z/OS environments: if you are using disks which do not permit a 23,476 blksize (i.e. 3350's), please notify us (cont.)<br />immediately so that we can create tapes for a smaller blksize (i.e. 17,600), or you can use the COPYMOD option of (cont.)<br />IEBCOPY to reblock from the tape to the disk loadlibrary as it is being loaded.<br />The library takes approximately 10 cylinders of space, they need directory entries sufficient for approximately 100 (cont.)<br />library members. You can save time by allocating that space before the installer arrives.<br />## <br />VSAM Space<br />The MAGEC repository consists of 24 VSAM KSDS files. They are all single key, fixed-length. The largest record length (cont.)<br />is 4K bytes, largest key length is 64 bytes. They normally use LSR in a CICS environment. The installer will punch out (cont.)<br />the IDCAMS (or AMSERV) DELETE and DEFINE control cards for all these files. You can prepare for the creation of the (cont.)<br />files by allocating (DEFINE SPACE) enough space (approximately 250 3380 cylinders) in a VSAM catalogue (create a new (cont.)<br />user catalogue, if desired). The space need not be contiguous and may be divided across several VOLUME ID's; however, (cont.)<br />excessive fragmentation may degrade performance. You may also choose to load the VSAM files into UNIQUE space, if you (cont.)<br />prefer.<br />The creation of the files is done using the IDCAMS control cards. The files are then initialized by executing a utility (cont.)<br />program provided by MAGEC (ALALDNUL). They are then loaded by executing another utility program (ALALDFIL) which reads (cont.)<br />the installation tape as input.<br />You could accomplish several tasks prior to the installer's arrival:<br />1.<br />Create the catalogue (if desired).<br />2.<br />Define the space.<br />3.<br />Have the JCL handy to execute IDCAMS, including appropriate user catalogue specs.<br />## <br />CICS<br />The MAGEC installer will punch, from the tape, the necessary PCT, PPT, FCT, and (optional) PLT entries for MAGEC. These (cont.)<br />are standard CICS macro specifications. You should be prepared to assemble these tables using the jobstreams you use (cont.)<br />for any other applications. If you are using RDO, you will want to assemble the tables and then import them since they (cont.)<br />would be tedious to enter manually. The PLT entry is to auto-start the MAGEC Spooler, you can omit it and then manually (cont.)<br />start it using an online transaction if you prefer.<br />The DD or DLBL statements for the MAGEC dictionary files must be included into your CICS start-up or (VSE-only) into (cont.)<br />standard labels, or (z/OS-only) as a filespec to the FCT entries (if you wish to alter them before assembling them). (cont.)<br />The DD or DLBL statements are also punched by the installer.<br />The new MAGEC library (discussed earlier) must also be concatenated into the CICS library search.<br />## <br />Training<br />The MAGEC Startup Program, a separately priced item which is usually purchased with the initial installation of MAGEC, consists of the following classroom courses:<br />Developing online applications using MAGEC<br />Customizing MAGEC-generated applications<br />Also, included with the standard MAGEC documentation is a full set of tutorials which illustrate actual development, customization, data definition, and security definition and control.<br />These tutorials and courses are of interest to *application developers*, *database administrators*, and *security officers.*<br />## <br />Professional Services<br />MAGEC Software can provide additional services ranging from basic consulting in the use of MAGEC through complete (cont.)<br />project direction and execution. MAGEC Software's professional consultants are experienced in the development of (cont.)<br />projects of any size. Many users feel that employing one or more of our professionals on their first large project adds (cont.)<br />a level of comfort and assurance and helps them to take advantage of the experience of others in similar (cont.)<br />efforts.<br />## <br />Support Calls<br />If you or your technical support personnel have any questions, please feel free to call us at one of the numbers below. The toll-free 800 numbers are valid in all of the contiguous United States.<br />1-214-202-4965<br />## <br />Execute-Only or Limited Versions<br />Some MAGEC users having multiple CPU's prefer to do all development on one CPU and to run production on the other(s). (cont.)<br />In some Corporate Licensing arrangements development functions might be contractually restricted to one (or several) (cont.)<br />CPU's. In those cases it is sometimes useful to install only a partial MAGEC system on the non-development CPU's. The (cont.)<br />central active dictionary is necessary at execution time for such features as the interactive help keys, security (cont.)<br />verification, automatic menu generation, and message handling and compression; however, many entities contained in the (cont.)<br />complete dictionary are unnecessary in an execute-only environment.<br />The disk space requirements are reduced (below the 200 cylinders recommended on the first page) if you are only installing a subset of the complete MAGEC system.<br />If you will not be doing any application development, you can greatly reduce the space requirement for the portion of (cont.)<br />the MAGEC dictionary used to store source code (the ALG file). This would represent a reduction of approximately 30 (cont.)<br />Megabytes.<br />If the above is true, you could also eliminate the freespace and over-allocation of most of the MAGEC files, since your (cont.)<br />environment will be more static and you will not be adding new specifications to the dictionary. The files involved are (cont.)<br />the SHD, SCF, MMP, MSK, DCL, ELT, DIT, and KYF.<br />In addition, if no development will be done using MAGEC, you might delete all the unused PPT entries. They are normally (cont.)<br />disabled by CICS at startup, anyhow. This saves only a few bytes each, but is neater than having unused (and (cont.)<br />never-to-be-used) PPT entries.<br />If you will not be using the MAGEC TP Spooling facility, you can eliminate the two files used by the Spooler (the SPL (cont.)<br />file and the RPH file). This would result in a further reduction of approximately 40 Megabytes.<br />In any case, *you should initially allocate the full 200 cylinders *in order to simplify the installation; then begin trimming the files after installation is complete.<br />Some MAGEC users may wish to create smaller, execute-only versions of MAGEC for the PC's. This can be done by removing (cont.)<br />all but the necessary run-time programs and by reducing the size of the ALG-file to its minimum (cont.)<br />size.<br />The fastest way to reduce the size of the ALG-file is to execute MAGINIT against it, thereby initializing the file to contain no records. This is done as:<br />MAGINIT ALG<br />&nbsp;<br />The minimum list of executable (program) files needed for an execute-only system is:<br />APLOAD<br />APUNLOAD<br />MAGINIT<br />DDAUDIT<br />**MMP650<br />MMP652<br />MMP653<br />MMP654<br />MMP661<br />MMP663<br />MMP636<br />MMP670<br />MMP675<br />MMP682<br />MMP684<br />MMP685<br />All of these files, of course, have an extension of .EXE and/or .DLL and are found in the MAGEC directory. You can (cont.)<br />delete (erase) any other of MAGEC's .EXE files, leaving only the above list plus your own application MMP's, etc.. It (cont.)<br />might also be a good idea to execute the CLEANLIB procedure (.BAT file) on the PC to erase any temporary files which (cont.)<br />may be left in the MAGEC directory.<br />&nbsp;<br /># <br />z/OS 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 IEBCOPY of complete MAGEC Load 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 ** z/OS 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 10-cylinder loadlibrary, BLKSIZE=23,476, with sufficient directory entry space for approximately 100 members. (cont.)<br />***Note: If you wish to follow our recommendations regarding a "test loadlibrary", please refer to the discussion in (cont.)<br />the z/OS Upgrade section.***<br />2.<br />Load the loadlibrary using IEBCOPY with the MAGEC.BACKUP tape as input. If you wish to alter the BLKSIZE, you can use the COPYMOD option of IEBCOPY, otherwise use the COPY option.<br />3.<br />Create the JCL named ALGTPCHX (see exhibit 1.1.5.1). Be sure to set the STEPLIB 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 ISPF (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 STEPLIB pointing to the new loadlibrary. The DD statements are in the member named VSAMDD 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 spooler files as well. The SYSOUT 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). You may wish to (cont.)<br />delete and uncatalog the SYS005 output file created earlier or just use a different DSN, this time. The output will (cont.)<br />contain a host of sample jobstreams for various MAGEC batch processes.<br />11.<br />Create ALALDEX JCL (see exhibit 2.3). Include the DD statements and STEPLIB.<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 ISPF (or another editor) to separate and tailor the jobstreams. They will have separator (cont.)<br />cards preceding each member, as before. In order to facilitate your tailoring, there are symbolic parameters coded in (cont.)<br />the sample jobstreams. You can use the global change facility of your editor to alter all occurrences of each symbolic (cont.)<br />to the appropriate value for your shop. If these do not accomplish 100% of what you desire, you can then use your (cont.)<br />editor to finish up the modifications.<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 DD statements (VSAMDD) to your CICS startup deck, unless you have altered the DFHFCT entries to include the (cont.)<br />DSNAME's. Add the MAGEC loadlibrary to the DFHRPL DD statement. Refer to exhibit 1.1.6.2.2.<br />16.<br /><br />next: install02.md.txt