gtps4m2a | System Generation |
This section outlines the hardware and software requirements that are
needed for running SIP.
SIP stage I may be executed on any system with MVS assembler capability,
subject to the following limitations:
The HLASM assembler is required for SIP stage I.
The amount of time needed to complete a stage I process is variable.
It depends on the machine processor model, the amount of work being done on
that machine, core size, version of the assembler, channel utilization, and
configuration. It is recommended that the stage I process be done
during a period of time when the system work load is at a minimum. A
system that can be totally dedicated to the stage I process will speed up the
process considerably.
Function
|
| Requirements (Minimum)
|
Input
| SYSLIB
| One DASD containing the concatenated data sets
ACP.SIPGEN.RELvv, and ACP.MACRO.RELvv, and
ACP.SYMACRO.RELvv.yyy.
- Note:
- In a multiple database function (MDBF) environment, data set
ACP.SYMACRO.RELnn.BSS must be concatenated to provide the
LOOK BACK facility required for nonbasic subsystem generations.
ACP.SYMACRO.RELnn.yy (where yy is the name of the
subsystem currently being generated) must be concatenated so that member
SYFCTB can be picked up from the FCTBG.
|
Input
| SYSIN
| One 80-column sequential data set containing the coded SIP stage I
macros.
|
Output
| SYSPUNCH
| Either 1 DASD or 1 tape drive for stage I output.
|
Output
| SYSPRINT
| One printer for assembly listing.
|
Work space
|
| DASD devices containing space for assemble work areas.
|
- Note:
- Because of the great number of modules being assembled, the region, time, and
workspace parameters should be coded at maximum values for performance
considerations.
SIP stage II may be executed on any system with MVS capability subject to
SIP user macro GENSIP operands and the following requirements:
- Function
- Requirements
- Operating System
- MVS/SP Version 1
- PL/I Compiler
- O (IEL0AA) -- XA Version
- C/C++ Compiler
- One of the IBM C or C++ compilers supported by the TPF system. See
TPF Migration Guide: Program Update Tapes for
more information about C/C++ compilers.
C and C++ programs that you want to trace using C function trace must be
compiled with the TEST option of one of the family of C/C++ compilers that are
supported by the TPF system.
The C/370 compiler is supported for migration purposes only.
SIP will create the JCL procedure SIPEDCC to call MASM. MASM can
execute multiple C and C++ compilations.
- Note:
- Before using SIPEDCC, check it to ensure it uses the data set naming
conventions of your installation. Update it as necessary.
Alternatively, copy the EDCC procedure used at your installation and name
it SIPEDCC. Change PGM=EDCCOMP on the EXEC statement to PGM=MASMvv
(where vv is the version code).
- Assembler
- HLASM
- Time
- Preset by stage I for each stage II job and step.
- Input stage II job stream
- The sequential data set as defined in stage I output as SYSPUNCH.
- Release Source Libraries
- One or more DASDs containing the release source code data sets.
- User Libraries
- One or more DASDs for user libraries (USRCE, USMAC, USOBJ parameters) that
must be cataloged data sets. User libraries must be blocked to 400 or
less. (BLKSIZE=400)
- Loader General File
- One DASD (LGFDV). See TPF Migration
Guide: Program Update Tapes for supported DASD types.
- Output SYSPRINT
- One printer for stage II output.
- LISTAPE parameter
- One tape drive for MASM assembly output, if requested (specified as
"UNIT=TAPE").
- ISO-C library for function stubs
- One stub for each C library function.
- DLM stub library
- One stub for each program called by a DLM.
- Object Library
- One DASD for release object library data set.
Notes:
- Any segments or modules that are shipped only as object code must already
be present in the object data set before the execution of stage II.
- IBM encryption modules BQKCIPH or BQKDES, if installed, before executing
SIP stage II (see CONFIG).
- Load Module Library
- One DASD for load module library data set.
- Note:
- As a minimum, only 2 devices are needed if the released source, and object
and load module data sets are allocated to the same DASD. It would even
be possible to allocate the user libraries to this same DASD, if space is
available.
- System Job Queue
- SYS1.SYSJOBQE data set of an MVS system must be defined large
enough to hold the largest SIP stage II job.
- System Data Sets
- SYS1.MACLIB and SYS1.AMODGEN must be available for use
during stage II processing. These data sets contain macros that are
needed for assembling certain TPF programs.
- Output Queue (SYSPRINT)
- Output from stage II is directed to the printer as follows:
- Offline programs
- A queue
- Control program
- K queue
- Real-time programs
- D queue
- Keypoints
- A queue
- TPF job execution
- A queue
Unless the OUTCL parameter is used in the GENSIP macro.
- Note:
- If the LISTAPE parameter of the GENSIP macro is coded, error free assemblies
will be directed to the tape, but listings with errors will be directed to the
appropriate queue.