next up previous contents index
Next: Tailoring the FATMEN Up: The FATMEN code Previous: Structure of the

Installing the FATMEN software

Installation of the FATMEN software consists of two steps:

  1. Installation of the FATMEN library (part of PACKLIB).
  2. Creation of the FATMEN shell program.

Installation of FATMEN on CERNVM

Generating the FATLIB library

The extraction of the code is made with the following PATCHY cradle:

+EXE.
+USE,QCDE.
+USE,*FATLIB,IBM.
+PAM,11, R=QCDE, T=A.ZEBRA
+PAM,12.       , T=A.FATMEN
+QUIT.
followed by the standard procedure to generate the TXTLIB, namely VFORT asm, EDITLIB asm, TXT GEN FATLIB asm.

The FATMEN module (for the command line interface)

The extraction of the code is made with the following PATCHY cradle:

+EXE.
+ASM,31.
+USE,*FMKUIP,IBM.
+USE,FMCDF,T=EXE,DIV.
+PAM,11, T=A.FATMEN
+QUIT.
which generates two files: the standard ASM file with the FORTRAN code and the diverted ASM2 file containing input to the KUIP processor. Both the ASM code and the output from the KUIP processor must be compiled and linked to build the FATMEN module.

The following exec has been used at CERN to perform the complete operation:

/**/
 Address Command
 'EXEC ZPATCHY FATMEN ( CRADLE(FATMEN) ASM(FATMEN) ASM2(FMCDF CDF)'
 
 'KUIPC FMCDF'  /* To generate the FORTRAN equivalent of the CDF file */
 
 'EXEC VFORT FATMEN'
 'EXEC VFORT FMCDF'
 'EXEC VFORT ENDMODU'         /* Dummy routine to "squeeze" the module*/
 'EXEC CERNLIB FATLIB ( LINK'
 
 'LOAD FATMEN FMCDF ( CLEAR NOAUTO'
 'INCLUDE ENDMODU'
 'GENMOD FATMEN ( TO ENDMODU'
 Exit
/*BEGIN ENDMODU FORTRAN */
      BLOCK DATA ENDMODU
      END

Processing the ORACLE routines for the FATMEN server

The ORACLE FORTSQL routines can be generated using the following cradles:

+EXE.
+ASM, 21,R=!./*BEGIN ! FORTSQL */
+USE,ORACLE.
+USE,*FATSQL.
+PAM,11.
+QUIT.
The output file should then be processed by the SPLITFIL command, which will create a separate file for each routine. These can then be pre-processed by the PCC exec as follows:

splitfile fatsql fortsql
-----> Split FATSQL FORTSQL A1 into pieces
Generate BLANKDEK FORTSQL A
Generate FMLOGI FORTSQL A
Generate FODEL FORTSQL A
Generate FOGET FORTSQL A
Generate FOPUT FORTSQL A
FAT3@cernvm;
pcc iname=fmlogi host=fortran
 
ORACLE Precompiler: Version 1.2.13.10 - Production on Thu Feb 22 17:32:04 1990
 
Copyright (c) 1987, Oracle Corporation, California, USA.  All rights reserved.
 
 
Precompiling FMLOGI.FORTSQL
FAT3@cernvm;
vfort fmlogi
VFORT compilation options in effect are: CHARLEN(32767) FLAG(W) GOSTMT OPT(2) 
MAP NOSDUMP.
File 'FMLOGI FORTRAN A1' will be processed.
VS FORTRAN VERSION 2 ENTERED.  17:32:07
 
**FMLOGI** END OF COMPILATION 1 ******
 
VS FORTRAN VERSION 2 EXITED.   17:32:10
 
FAT3@cernvm;

Generating the code for the FATMEN server

This code can be generated with the following cradle:

+USE,IBM,*SQL,*FATSRV.
+EXE.
+PAM,11, R=QCDE, T=A.  ZEBRA PAM *
+PAM,12,  T=A. FATMEN PAM *
+QUIT.
The server module can then be built as follows:

CERNLIB V5ORAFIX V5ORACLE FATLIB
LOAD FATSRV OSDDAT OSDU2OS (CLEAR NOMAP NODUP NOAUTO)
GENMOD FATSRV

Generating the FATMEN server for remote VM systems

This is performed in the same way as on CERNVM with the following exception:



next up previous contents index
Next: Tailoring the FATMEN Up: The FATMEN code Previous: Structure of the


Janne Saarela
Mon May 15 09:59:59 METDST 1995