gtpd2m0f | Data Communications Services Reference |
This program uses fixed file records to maintain load module images on the system. The size and description is in the 3705 Keypoint Record (produced by SIP macro SKCC0C). Large, long-term file pool records are used to maintain images of the dump records. The description of the record type is in the 3705 Dump Record (CD0DC). Tape files are used as the vehicle for carrying data between the TPF system and MVS; these files are in the 3705 Dump File and 3705 Load File (both produced by SIP macro SKCC0C).
All functions are designed to be initiated by a command. In addition, the load and dump of the 3705 Controller can be initiated by a system restart or by an interrupt from the 3705. This interrupt can be generated by the 3705 Control Program or by pressing the load button on the 3705 Controller. The input message specifies the function to be activated and, depending on the function, the 3705 control unit address and/or the load module name to be acted upon.
Procedurally, a load module must be placed on the TPF files before it can be loaded into a 3705 Controller. Therefore, an interrupt load should never occur unless a load module is maintained for it. A 3705 Controller can be placed online with a load module already loaded into it. The initial load to the TPF files must contain the 3705 resident support (load and dump) programs. Subsequent loads may or may not contain these programs.
Various messages issued by each phase of this function will indicate the status of that phase; that is, successful completion, processing error, missing input parameter, etc. The output of the dump-purge function is a dump tape which is used as input to an offline routine to format and print the dump(s).