gtpm2m27 | Migration Guide: Program Update Tapes |
The following section discusses the migration considerations for tape record migration.
See the APEDIT for APAR PJ26577 for information about prerequisite APARs.
Tape record migration permits tape records to be migrated to file address compute (FACE) program table processor unique fixed file record types, which removes the constraints that are imposed by the current method of ordinal-based processor uniqueness. Changes to the ZTDEV command and tape restart support the migration and initialization of tape records to processor unique fixed file record types.
Ordinal-based processor uniqueness for fixed file record types means that adding processors is both difficult and time-consuming. Processor unique fixed file record types alleviate the problem of allocating and managing ordinals when you are changing the number of generated processors in your complex.
Updates in tape support affect the following areas:
Current tape support for the TPF 4.1 system uses the following three fixed file record types to store tape records:
All of these record types use ordinal-based processor uniqueness; that is, each processor is allocated specific ordinals to simulate processor unique records. Tape record migration uses FACE table processor unique fixed file record types that are independent of ordinal allocation.
When tape record migration is installed, tape support for a processor uses three new processor unique fixed file record types to store tape records. Records from the ordinal-based fixed file record types must be migrated to the processor unique fixed file record types or the processor unique fixed file record types must be initialized. When a processor enters tape restart, each of the processor unique fixed file record types for that processor is migrated or initialized.
Processor unique fixed file record types are as follows:
Changes to the FCTBG support the new fixed file record types and provide a method to verify these record types.
A processor complex can have a combination of processors, where some processors are using the processor unique fixed file record types and some are using the ordinal-based fixed file record types. Processors without tape record migration installed continue to use and update ordinal-based fixed file record types. Processors that have tape record migration installed (migrated processors) use the processor unique fixed file record types and ignore any ordinal-based fixed file record types.
There are constraints for the capture and restore utility in a complex with a combination of processors. The capture utility captures both the #TLDMR and #TPLBL fixed file record types for the primary subsystem user in the current subsystem. After the first processor in the processor complex has completed tape record migration, the capture utility must capture #TLDMR records for the processors that are using ordinal-based fixed file record types and #TPLBL fixed file records for the processors that are using processor unique fixed file record types. Because only the migrated processor recognizes the #TPLBL fixed file record types, a migrated processor must be the primary capture processor. The restore utility must be run from a migrated processor for the same reason.
There are none.
The following section summarizes interface changes.
The following section summarizes C/C++ language changes. This information is presented in alphabetic order by the type of C/C++ language information. See the TPF C/C++ Language Support User's Guide and TPF Application Programming for more information about the C/C++ language.
There are no changes.
There are no changes.
Table 708 summarizes the general use C/C++ language header file changes. This information is presented in alphabetic order by the name of the general use C/C++ language header file.
General use means these header files are available for your
use.
Table 708. Changes to General Use C/C++ Language Header Files for Tape Record Migration
C/C++ Language Header File | New, Changed, or No Longer Supported? | Do You Need to Recompile Segments? |
---|---|---|
c$fbd0.h | Changed | Yes; you need to recompile FTPS03. |
c$fer0.h | Changed | No |
c$fva0.h | Changed | No |
c$syseq.h | Changed | No |
There are no changes.
There are no changes.
There are no changes.
There are no changes.
There are no changes.
There are no changes.
There are no changes.
Table 709 summarizes the copy member changes. This information
is presented in alphabetic order by the name of the copy member.
Table 709. Changes to Copy Members for Tape Record Migration
Copy Member | Type | CSECT Where Copy Member Is Located | DLM Where CSECT Is Located | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|---|---|
TPFGBL | Not Applicable | Not Applicable | Changed | Added a global equate to support new fixed file record types. |
Table 710 summarizes fixed file record changes. This
information is presented in alphabetic order by the name of the fixed file
record.
Table 710. Changes to Fixed File Records for Tape Record Migration
Fixed File Record | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|
#IBMMP4 | New | Created by tape record migration. |
#IBMM4 | Changed | The tape group definition table (TGDT) was moved from this fixed file record type to the #IBMMP4 fixed file record type. |
#TDATR | No Longer Supported | Not Applicable. |
#TDTDR | New | Created by tape record migration. |
#TLDMR | No Longer Supported | Not Applicable. |
#TPLBL | New | Created by tape record migration. This record defaults to nonrestorable, as defined by the RAMFIL macro with the RESTORE parameter specified. |
The following section summarizes the macro changes. This information is presented in alphabetic order by the type of macro.
There are no changes.
There are no changes.
Table 711 summarizes the data macro changes. This information
is presented in alphabetic order by the name of the data macro.
Table 711. Changes to Data Macros for Tape Record Migration
Data Macro | New, Changed, or No Longer Supported? | Do You Need to Reassemble Programs Using This Data Macro? |
---|---|---|
ITDAT | Changed | No |
ITDVRT | Changed | No |
ITGDT | Changed | No |
There are no changes.
Table 712 summarizes the selected equate macro changes. This
information is presented in alphabetic order by the name of the selected
equate macro.
Table 712. Changes to Selected Equate Macros for Tape Record Migration
Selected Equate Macro | New, Changed, or No Longer Supported? | Do You Need to Reassemble Programs? |
---|---|---|
SYSEQ | Changed | No |
TAPEQ | Changed | Yes; you need to reassemble COSM. |
There are no changes.
Table 713 summarizes the system initialization program (SIP) skeleton
and internal macro changes. This information is presented in alphabetic
order by the name of the SIP skeleton and internal macro. If the SIP
skeleton and internal macro (inner macro) is changed, you must reassemble the
SIP Stage I deck and run the appropriate job control language (JCL) jobs from
the SIP Stage II deck.
Table 713. Changes to SIP Skeleton and Internal Macros for Tape Record Migration
SIP Skeleton and Internal Macro | New, Changed, or No Longer Supported? |
---|---|
GENR | Changed |
SPPGML | Changed |
There are no changes.
Table 714 summarizes system initialization program (SIP) Stage II
macro changes. This information is presented in alphabetic order by the
name of the SIP Stage II macro. If IBMPAL is changed, you must run the
system allocator (SALO) and load the new program allocation table
(PAT) to the TPF 4.1 system.
Table 714. Changes to SIP Stage II Macros for Tape Record Migration
SIP Stage II Macro | New, Changed, or No Longer Supported? |
---|---|
IBMPAL | Changed |
There are no changes.
There are no changes.
There are no changes.
Table 715 summarizes segment changes. This information is
presented in alphabetic order by the name of the segment.
Table 715. Changes to Segments for Tape Record Migration
Segment | Type | Link-Edit Module (Where Offline Segment Is Linked) | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|---|
BXBL | Real-Time Assembler | Not Applicable | Changed | Updated to capture #TLDMR and #TPLBL fixed file record types. |
CORB | Real-Time Assembler | Not Applicable | Changed | Updated to provide future support for more than eight loosely coupled processors. |
CORK | Real-Time Assembler | Not Applicable | Changed | Added new messages to support migrating and initializing tape records from ordinal-based fixed file record types to FACE table processor unique fixed file record types. |
COSA | Real-Time Assembler | Not Applicable | Changed | Updated to support the #TPLBL fixed file record type. |
COSB | Real-Time Assembler | Not Applicable | Changed | Updated to support the #TDTDR fixed file record type. |
COSD | Real-Time Assembler | Not Applicable | Changed | Updated to support the #TPLBL fixed file record type. |
COS5 | Real-Time Assembler | Not Applicable | Changed | Added support for the ZTDEV command with the MIGRATE and CLEAR parameters. |
COS6 | Real-Time Assembler | Not Applicable | Changed | Updated to provide support for the #IBMMP4 and #TDTDR fixed file record types. |
COS7 | Real-Time Assembler | Not Applicable | Changed | Updated to provide support for the #IBMMP4 and #TDTDR fixed file record types. |
COS8 | Real-Time Assembler | Not Applicable | Changed | Updated to provide support for the #TDTDR fixed file record type. |
COTH | Real-Time Assembler | Not Applicable | Changed | Updated to provide support for the #TPLBL fixed file record type and to move the TPLD and TLMR record initialization routine to the COT9 segment. |
COTK | Real-Time Assembler | Not Applicable | Changed | Updated to provide support for the #IBMMP4 fixed file record type. |
COT1 | Real-Time Assembler | Not Applicable | Changed | Updated comments only; no code changes were made. |
COT2 | Real-Time Assembler | Not Applicable | Changed | Added support to migrate TGDT and DTDAT records from the ordinal-based fixed file record type to the FACE table processor unique fixed file record type. |
COT3 | Real-Time Assembler | Not Applicable | Changed | Added support to migrate TPLD and TLMR records from the ordinal-based fixed file record type to the FACE table processor unique fixed file record type. |
COT5 | Real-Time Assembler | Not Applicable | Changed | Added support for the ZTDEV command with the MIGRATE and CLEAR parameters. |
COT9 | Real-Time Assembler | Not Applicable | New | Supports the migration and initialization of tape records from ordinal-based fixed file record types to FACE table processor unique fixed file record types. |
FTER00 | C Language | FCTBG | Changed | Added messages to support the new fixed file validation routine. |
FTVA02 | C Language | FCTBG | Changed | Added validation to support processor and subsystem user unique record types. |
FTVA03 | C Language | FCTBG | Changed | Updated all record definitions to include a new field and added new record definitions. |
The following section summarizes system equate changes.
Table 716 summarizes changes to equates that are not configuration
dependent (in SYSEQ). This information is presented in alphabetic order
by the name of the SYSEQ tag.
Table 716. Changes to SYSEQ Tags for Tape Record Migration
SYSEQ Tag | Equate Value | New, Changed, or No Longer Supported? |
---|---|---|
TGDTORD | 0 | Changed |
TGDTORD_OLD | 93 | New |
There are no changes.
The following section summarizes functional and operational changes. This information is presented in alphabetic order by the functional or operational change.
See Appendix A, "PUT 2-15 Interface Changes by Authorized Program Analysis Report (APAR)" for a summary of functional and operational changes by APAR.
Table 717 summarizes command changes. This information is presented in alphabetic order by the name of the command. See TPF Operations for a complete description of all commands.
Attention: Changes to commands can impact any automation
programs you are using in your complex.
Table 717. Changes to Commands for Tape Record Migration
Command | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|
ZTDEV | Changed | Added the MIGRATE and CLEAR parameters. |
Table 718 summarizes message (offline and online messages) and system error changes.
The message IDs or system error numbers are listed in numeric order preceded by their alphabetic prefix. Some offline and online messages do not have a standard message ID. For these, the messages are presented in alphabetic order based on the initial message text; or for those messages that begin with variable information, the initial message text that follows that variable information. See Messages (System Error and Offline) and Messages (Online) for a complete description of all messages and system errors.
Attention: Changes to offline messages, online messages,
and system errors may impact any automation programs you are using in your
complex.
Table 718. Changes to Messages and System Errors for Tape Record Migration
Message ID or System Error Number | Message Type | New, Changed, or No Longer Supported? |
---|---|---|
000762 | System Error | Changed |
000764 | System Error | Changed |
COTH0093W | Online | Changed |
COT20383A | Online | New |
COT20384I | Online | New |
COT20385I | Online | New |
COT50007I | Online | New |
COT50008I | Online | New |
COT90093W | Online | New |
COT90386I | Online | New |
COT90387I | Online | New |
COT90388W | Online | New |
COT90389I | Online | New |
COT90390I | Online | New |
FCTB0120E | Offline | New |
FCTB0121E | Offline | New |
There are no changes.
There are no changes.
Run the file address compute (FACE) program table generator to produce a new FACE table. Run SIP to verify the new fixed file records.
See TPF System Generation for more information about the FACE table generator and SIP.
There are no changes.
There are no changes.
Table 719 summarizes changes to the publications in the TPF
library. This information is presented in alphabetic order by the
publication title. See the TPF Library Guide
for more information about the TPF library.
Table 719. Changes to TPF Publications for Tape Record Migration
Publication Title | Softcopy File Name | Description of Change |
---|---|---|
TPF Database Reference | GTPDBR09 | Updated with information about TPLD and TLMR fixed file records not being restored for tape record migration. |
Messages (System Error and Offline) and Messages (Online) | Not Applicable | Updated with information about messages that were added for tape record migration. |
TPF Migration Guide: Program Update Tapes | GTPMG201 | Updated with migration considerations for tape record migration. |
TPF Operations | GTPOPR0B | Updated with information about the commands that were added and changed for tape record migration. |
TPF System Generation | GTPSYG0B | Updated with information about the fixed file records that were added or are no longer supported for tape record migration. |
There are no changes.
There are no changes.
There are no changes.
There are no changes.
There are no changes.
Use the following procedure to install tape record migration on your TPF 4.1 system.
See TPF System Generation for more information about the RIAT.
See TPF System Generation for more information about the RAMFIL macro.
Each SSU is processed independently; for example, the TLMR and TPLD records might be initialized for one SSU and migrated for another SSU on the same IPL.
If the MIGRATE parameter is specified, the TPF 4.1 system tries to migrate the DTDAT records from the #TDATR fixed file record type to the #TDTDR fixed file record type; the TPF 4.1 system clears the records if the DTDAT records in the #TDATR fixed file record type are not valid or if it cannot access the #TDATR fixed file record type.
If the CLEAR parameter is specified, the DTDAT records in the #TDTDR fixed file record type are cleared. Clearing the DTDAT records permits tape restart to initialize the DTDAT records in the #TDTDR fixed file record type when tape restart continues.
When all processors in the complex are IPLed, the #TLDMR and #TDATR fixed file record types can be removed. These record types are only required when nonmigrated processors are active in the complex or when nonmigrated processors need to migrate these records to the new record type.