limes datentechnik gmbh Louisenstr. 21 D 61348 Bad Homburg Tel. ++49 6172-59190 Fax ++49 6172-591939 eMail support@flam.de http://www.flam.de http://www.limesdatentechnik.de ******************************************************************************************* * * * >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 25 years FLAM <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<* * * * >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 20 years FLAM subsystem <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<* * * ******************************************************************************************* Dear FLAM-User, the new FLAM subsystem version FLAM-sub V4.4A ist stored in this directory. FLSUB44A.ADC This FLAMFILE contains all files and libraries of FLAM-sub V4.4A: FLAM.FLSUB44A.JOBLIB Job Library FLAM.FLSUB44A.LOAD Program library FLAM.FLSUB44A.HANDBUCH.PDF Manual in PDF format (binary, german version) FLAM.FLSUB44A.MANUAL.PDF Manual in PDF format (binary, english version) Please transfer the FLAMFILE FLSUB44A.ADC on to the MVS- (OS/390-, z/OS-) Hostsystem. You can use any filetransfer that is able to transfer binary records of fix 512 bytes without any translations (IND$FILE, FTP, ...). All files will be created and allocated by FLAM during decompression of the FLAMFILE. The FLAMFILE has been AES-encrypted during compression. Please use the key that was sent with this delivery. If the original file names do not fit to your organization you can change them during decompression: //DEC EXEC PGM=FLAM,PARM='D,FLAMO=' //STEPLIB DD DSN=user.FLAM.LOAD,DISP=SHR //FLAMFILE DD DSN=user.FLSUB44A.ADC,DISP=SHR //FLPRINT DD SYSOUT=* //FLAMPAR DD * CRYPTOKEY=... /* Here all names with 'FLSUB44A.' will be changed, starting with 'user' as first qualifier, and 'pref' as second qualifier. The rest of the names remain unchanged (for further details see 3.1.4.3 in the FLAM-utility manual). Examples: 1) Yout userid is 'E24AM', you do not want to change any other qualifiers in the names. Then the parameter for decompression is: FLAMO= Then following file names are created: E24AM.FLSUB44A.JOBLIB Jobs E24AM.FLSUB44A.LOAD Programs . . 2) Your userid is 'E24AM', the 2. qualifier shall be changed to 'FLAMSUB.V4R4M0'. Then the parameter for decompression is: FLAMO= Then following file names are created: E24AM.FLAMSUB.V4R4M0.JOBLIB Job Library E24AM.FLAMSUB.V4R4M0.LOAD Program Library . . . Note: Using FLAM 4.2 or higher for decompression, you can define the Volume where all data are to be stored entering OVOLUME=volume,OUNIT=unit or OSTORCALS=class as FLAM-parameter. Manuals: ======== In addition to the MVS version the manuals are stored in a directory for usage on a PC system (Unix, Windows, ...). You will find them in \FLAM-sub\MANUAL. After decompression the FLAMFILE on the host, manuals are stored to disk as a PDF document These host files are used as an archive for any user to download them on to a PC (binary mode!). Licensation: ============ FLAM-sub V4.4A requires a valid licence for FLAM-Utility. Installation: ============= Please see chapter 9 in the manual. Here a short summary: After decompression and decryption, all subsystem load modules must be stored in an APF authorized LOADLIB and must be concatenated to SYS1.LINKLIB, i.e. updating the member LNKLSTxx, IEAAPFxx, or PROGxx of SYS1.PARMLIB. The subsystem loads during OPEN modules from the FLAM utility, so that library must have the same prerequisites (it is recommended to copy all modules of the utility and subsystem in one library and to use only that one). Start of FLAM subsystem ======================= - It is recommended to use the started task to activate FLAM subsystem (see example JOBLIB(FLAM)): S FLAM It will be easier to update newer versions in the future. - It is possible to start FLAM subsystem via the consol command SETSSI ADD,S=FLAM,I=FLSSIPL - Update the member SYS1.PARMLIB(IEFSSNxx) to start the subsystem during next IPL (see example JOBLIB(IEFSSN0F)). Update of an existing FLAM subsystem: ===================================== a) Start was done during IPL by the member IEFSSNxx Please copy all new modules into the existing LOAD library, or delete the library from the LINKLST and add the new one. Next IPL starts the new FLAM subsystem. b) Start was done by a started task Attention: Please take care that there is no active job using the subsystem! - Please stop the subsystem entering P FLAM from the console - Copy all modules (utility and subsystem) into the existing LOAD library - Refresh the directory LLA REFRESH - Start the subsystem again S FLAM Starting jobs using the subsystem is now allowed. Test the new version in an existing FLAM subsystem environment: =============================================================== First of all, it is impossible to start two subsystems using the same name. But it is allowed to change the subsystems name to any other name (up to 4 character long) to test FLAM subsystem. This name has to be used in all testjobs using the subsystem. Please copy all subsystem- and utility modules in one authorised library, and update the started task as following (name MALF is assumed): //MALF PROC SSN=MALF //SMALF EXEC PGM=FLSSTSK,PARM=&SSN,TIME=NOLIMIT //STEPLIB DD DSN=new.authorised.library,DISP=SHR Start the subsystem entering 'S MALF', stop it with 'P MALF'. Each testjob requires the STEPLIB from above, so all STEPLIBs must be authorised as well! Example for testing MALF: //STEP1 EXEC PGM=IEBGENER //STEPLIB DD DSN=new.authorised.library,DISP=SHR //SYSIN DD DUMMY //* input file: //SYSUT1 DD DSN=FLSUB44A.JOBLIB(TESTJOB),DISP=SHR //* output file: //SYSUT2 DD SUBSYS=(MALF,'FLAMDD=NEWDAT') //* FLAMFILE: //NEWDAT DD DSN=new.file, // DISP=(NEW,CATLG), // ... Note: ----- Do not concatenate the 'new.authorised.library' to LINKLIB! The older and the new version both load the same named modules, so unpredictable results will occur, depending on the sequence order of the libraries in the concatenation! Summary of changes FLAM-sub V4.4 ================================ Within FLAM-sub V4.4 the 'Key Management Exit Interface' is implemented (like the FLAM utility, see manual FLAM V4.4, ch. 3.5.5). With this method it is possible to connect FLAM-sub to a key management system. The used key for encryption / decryption is never protocolled and seen in the jes-log. limes datentechnik gmbh, August 2012