900 Series HP 3000 Computer Systems Migration Process Guide ABCDE HP Part No. 30367-90007 Printed in U.S.A.
The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or tness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Printing History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions.
iv
Preface MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers. In HP documentation and in talking with HP 3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX.
vi
Conventions vii
UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command Command COMMAND It cannot, however, be entered as: comm italics com_mand comamnd In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value.
Conventions (continued) [ ... ] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...
1 Introduction This chapter introduces the migration stages. In order to help organize the activities involved in the migration process, a six-stage migration process is de ned as follows: 1. Education 2. Analysis and planning 3. Preparation 4. Installation 5. Compatability Mode (CM) operation 6. Native Mode (NM) operation These stages should be used as a guideline for migration. Stages can, and often will, overlap or be skipped altogether. Figure 1-1 summarizes the migration project stages.
Figure 1-1.
Hewlett-Packard has provided solutions to ease the migration process at each stage: use the Migration Toolset during the analysis/planning stage, the Directory Migration Tool (DIRMIG) to migrate the operating environment during the installation stage, and the Switch Assist Tool (SWAT) to create mixed-mode applications during the migration to NM. You will nd other migration documents and tools listed in Chapter 2.
Analysis and Planning During analysis and planning, the second stage of the migration process, the team develops the migration plan. Thorough analysis and planning is crucial to the success of migration. Phased migration requires analysis of the existing application environment, consideration of MPE/iX functionality requirements and dependencies, and careful planning based on migration options available, time and resources required, and desired performance.
You can estimate the migration e ort needed by analyzing how many incompatibilities you nd and how many changes are required to work around them. The analysis also determines the migration schedule and strategy you form for each application and database. Planning During planning, the team de nes migration schedules and strategies for migrating each application and database. If application will be migrated in phases, the strategy describes those phases.
4. Modify applications to access NM 32-bit data. Preparation During preparation, the third stage of the migration process, you update software to make migration easier. This stage may span the entire migration process. It can start before the 900 Series arrives. Preparation involves updating to more recent versions of MPE software and HP products. For example: The MPE V/E-based system must be updated to U-MIT or later software prior to migrating to the 900 Series HP 3000.
Installation During installation, the fourth stage of the migration process, your 900 Series HP 3000 is installed and con gured, and all programs and les are moved to the new machine. The objective is to have a functional MPE/iX-based system in place in order to begin the migration. Use the Directory Migration Tool (DIRMIG) to migrate the MPE V/E operating environment.
Native Mode Operation Native Mode operation is the sixth, and nal, stage of the migration process. The objective of this stage is the implementation of the migration plan so that it meets your goals and performance expectations. The length of this stage depends on the scope of the migration plan, the strategy chosen, and the extent of changes that must be made to the application to meet performance goals and user expectations.
can be accessed by applications executing in NM only through the Switch subsystem. At the end of this phase, check performance of the application which uses Switch. If it does not met the goals de ned in the migration plan, you may need to modify the plan to include an additional phase. During this additional phase, you would convert the CM procedures to NM. Recompile CM procedures to NM if possible. If the CM procedures are implemented in a language not supported in NM you will have to rewrite them.
2 Education This chapter discusses the rst stage of migration: the education stage. It includes: \Migration Project Team", a de nition of the project team you should form to complete migration. \System Overview", an introduction to the 900 Series HP 3000 hardware and software. \Migration Options and Solutions", a discussion to help you plan your migration methods. \Migration Tools and Documents", a list of Hewlett-Packard products available to help you migrate.
Include one or more representatives from each area in your migration project team, depending on the focus and extent of your migration. The most important keys to a successful migration e ort is careful planning and a working knowledge of the existing applications and installations needs. The migration team must fully understand the migration options and the rami cations of migrating some applications and not others.
System Overview Before describing the options and issues involved in migrating to a 900 Series HP 3000 Computer System, it is important to understand the hardware and software components of the system. The 900 Series HP 3000 family is based on HP Precision Architecture (HP-PA), an architecture founded on the concepts of RISC (Reduced Instruction Set Computer). The operating system for the 900 Series family is MPE/iX (MPE with extended large addressing).
superset of MPE V/E features, some incompatibilities exist due to fundamental di erences between the systems software and hardware. MPE/iX provides two environments (modes) for program execution: Compatibility Mode (CM) and Native Mode (NM). Program execution is not restricted to operating entirely in CM or NM; a program operating in one mode can call procedures that operate in the other. This switching between CM and NM is called mixed-mode operation.
If you run MPE V/E programs on MPE/iX, you will get better performance using OCT than you will using the emulator. With the emulator, instructions have to be fetched and decoded each time the program is run. You can cut overhead signi cantly by directly executing object code that OCT has already translated and appended to the program le. The OCT translated le saves both the original program and the translation. This means the resulting le can be executed on both MPE V/E-based and MPE/iX-based systems.
NM to call procedures which reside in CM Segmented Libraries (SLs). Switch also allows CM programs to call procedures located in NM Executable Libraries (XLs). The Switch subsystem resolves the di erences between NM and CM execution through a set of intrinsics that provide mixed-mode execution access. The switching is transparent to the user. Because MPE/iX can mix modes of execution, applications to be migrated in phases, using CM as an intermediate step between MPE V/E and NM.
Figure 2-1. Summary of Phased Migration Migration Options and Solutions You will need to develop strategies to migrate your users' operating environment, data, programs, and databases. Hewlett-Packard has de ned various migration options, created various tools, and outlined various strategies to help you to this successfully.
Migrating the Operating Environment The user's operating environment contains: directory accounting structure. User De ned Command (UDC) structure. private volume con gurations (volume sets and media). global Resource Identi cation Number (RIN) con gurations. user logging identi ers. user les. Hewlett-Packard recommends the use of the Hewlett-Packard supplied directory migration tool, DIRMIG, to migrate your MPE V/E operating environment to MPE/iX.
Data (\ at") les generally contain byte streams of data. When the data is read by a program, the program interprets the data according to the program's internal data structures. The data structures are aligned by compilers, as de ned by the program, using the system's natural alignment. When MPE V/E programs are compiled to NM, the natural alignment changes from 16 bits to 32 bits. But the data in the les (the byte stream) does not change.
formats for representing oating-point real numbers: HP 3000 format is the default in CM, and IEEE format is the default in NM. MPE V/E programs running in CM are not a ected by the incompatability. For mixed-mode programs, select HP 3000 oating-point representation or IEEE oating-point representation by using the same compiler options and directives that are used to select data alignments. However, if full NM performance and precision is necessary, you need to convert all oating-point data to IEEE format.
and UDCs to use the NS3000/V subsystem. (All NS3000/V features are supported by NS3000/iX.) Migrate all applications, job les, and UDCs directly to MPE/iX and convert them to use the NS3000/iX subsystem. Migrating Programs The phased approach to migrating MPE V/E-based programs to NM over time allows your migration project team several options to achieve their goals.
non-Privileged Mode MPE V/E programs and data can be restored to an MPE/iX system and run in CM without the need for recompilation. CM o ers a variety of MPE V/E compatible compilers, such as COBOL II/V, HP FORTRAN 77/V, Pascal/V, BASIC/V, and HP Business ASIC/V. The MPE V Segmenter is available for building and maintaining program and library les for execution in CM on the 900 Series. After recompiling the application, it is suggested that you thoroughly test the application to ensure valid results.
Hewlett-Packard recommends that programs be recompiled with level 0 optimization, tested, and subsequently recompiled with other optimization levels. Refer to the appropriate language reference manual for speci c details on compiler optimization. Migrating SPL programs to NM is more complex. Due to its dependence on the architecture of MPE V/E-based systems, an NM SPL compiler is not supported by Hewlett-Packard.
CM. The NM program, however, must access the SL procedures via the MPE/iX Switch subsystem because SLs are not directly accessible by programs executing in NM. Switching between modes usually does not require source code modi cations. In most cases, a program is recompiled to NM while the libraries accessed by the program remain in CM. A switch stub is required for every procedure that the program accesses from the CM SL. These switch stubs are placed in a NM library which is linked with the program.
which still remain in CM SLs. Switch is also needed by developers of new NM applications that require the services of CM SL procedures. If application size is a consideration, performancesensitive portions of the CM application may be rewritten or recompiled in NM rst, allowing CM programs to continue to call the procedures.
1. On the MPE/V side, use the ISQL UNLOAD command with the EXTERNAL option to create ASCII le containing all data currently stored in each table in the DBEnvironment. 2. Copy the ASCII les and the description les created by the UNLOAD command over to the MPE/iX system. You can STORE and RESTORE the les, or you can use a disk copy utility. 3. Re-create the DBEnvironment on the MPE/iX system. Be sure to create tables with the same column descriptions as in the MPE V DBEnvironment. 4.
Additional information on migrating TurboIMAGE/V databases can be found in Appendix H. With this option, you move your data to TurboIMAGE/XL in NM, and your applications to CM. The CM programs rely on MPE V/E object code compatibility. In most cases, the programs and databases are restored from an MPE V/E STORE tape. Option 1: CM. This option has several advantages: MPE V/E program les run with few or no modi cations. The TurboIMAGE/XL database can be immediately accessed by the program.
The application's performance may improve over CM execution. The TurboIMAGE/XL intrinsic calls remain intact. The database is compatible with MPE V/E-based systems. Therefore, programs that access the same database can be systematically migrated to NM without impacting productivity of other CM programs accessing the database. Remote TurboIMAGE/XL access is preserved. Figure 2-2.
Migration Documents General Information Manual (5954-7418) provides a general overview of the 900 Series HP 3000 family. HP 3000 Computer Systems System Con guration Guide (5954-9354) provides current information on supported peripherals. Introduction to MPE XL for MPE V Programmers (30367-90005) updates programmers on topics that have changed from MPE V/E to MPE/iX and pertain to the MPE programming environment. This manual is useful when analyzing incompatibilities detected by the Migration Toolset.
Migration Training FastLane 3000 is a Hewlett-Packard consulting service that helps you achieve more e cient use of time and resources as you migrate your application to the 900 Series HP 3000 system. It helps you understand how the migration process could impact your particular data processing environment, and what actions you can take to streamline that process.
as output. Operation of OCA is discussed in Appendix B, \Using the Object Code Analyzer". RTM, available on MPE V/E-based systems, provides customers with a list of run-time incompatibilities by monitoring applications as they execute on an MPE V/E-based system and logging incompatibilities as they occur. Operation of RTM is discussed in Appendix C, \Using the Run Time Monitor". Directory Migration Tool (DIRMIG) is an MPE/iX tool that migrates the operating environment.
DBCONV is a utility that will convert your IMAGE/3000 database to a TurboIMAGE database. SDCONV is a program that converts and loads data from Dictionary/V to HP System Dictionary/iX.
3 Analysis and Planning This chapter discusses the second stage of migration: analysis and planning. During this stage, you gather and analyze the applications to be migrated so that you know how much time and e ort you will need to migrate. At the end of this stage you will have your migration plan based on this analysis. This phase, then, involves two activities : Analyzing the applications Planning the migration Careful and thorough analysis will ensure a successful migration plan.
Detecting Incompatibilities Use the Migration Toolset during the analysis and planning stage. Using the tools, you can detect most migration-related problems in MPE V/E les before you migrate them to an MPE/iX-based system. Some problems cannot be detected by the Migration Toolset. They can only be determined by someone who has a working knowledge of what the application does and how it does it. These problems are summarized in Appendix D, \Incompatibilities".
Using the static search method, program and SL les are searched for instances of calls to external procedures and system intrinsics that may cause problems when the object code is executed on an MPE/iX-based system (either in CM or when recompiled in NM). This method reports an incompatibility whether or not the call is executed at run time. Two migration tools, MPT and OCA, report on incompatibilities found using the static search method of detection.
Migration Planning Tool MPT provides a rst look at the potential issues arising from migrating les from an MPE V/E-based computer system to an MPE/iX-based computer system. MPT is not intended to be all-encompassing, but rather a vehicle for providing a sense of direction to the migration process. MPT is easy to use by inexperienced programmers and analysts, yet provides in-depth detail for more sophisticated users.
consequences related to system performance. Its purpose is to assess disk capacity requirements and to uncover incompatibilities that might a ect the migration e ort. Refer to Appendix I, \Using the Migration Planning Tool" for detailed information about MPT. Object Code Analyzer OCA is a utility to aid in migrating application programs from an MPE V/E-based HP 3000 (running U-MIT or later) to an MPE/iX-based HP 3000.
then determine the procedure and the o set within the procedure by using a PMAP to trace an incompatibility back to a location in the source code. This information simpli es the task of identifying the exact location of the incompatibility. By examining each of these locations you can determine if a true incompatibility exists. Refer to Appendix B, \Using the Object Code Analyzer" for detailed information about the OCA.
Using RTM, you can: Identify incompatibilities independent of the source language. Trap all events from all library and program paths executed. Trace an event to the code segment and o set in code. Use this information, with a PMAP and source listing, to locate the incompatibility. Flag a potential problem in cases where return codes or values have been modi ed for MPE/iX. However, no incompatibility exists if your program does not depend on the modi ed return value.
Reporting on incompatibilities found in job stream les and UDC les as well as in program and SL les. OCA is best suited for:. Analyzing all programs and SL les to be migrated to a 900 series HP 3000. Detecting incompatibilities in code paths that may not have been executed while RTM was enabled. Locating calls to user-selected external procedures. Quickly determining potential incompatibilities. Detecting calls to unsupported routines. RTM is best suited for:.
Potential incompatibilities reported by MPT and OCA can fall into one of four categories. These categories relate to whether the event was executed while RTM was in e ect and if the event detected by MPT or by OCA is a real incompatibility. An incompatible event did not execute while RTM was enabled. A compatible event did not execute while RTM was enabled. An incompatible event executed, and was detected and logged by RTM. A compatible event executed, and was detected but not logged by RTM.
Your migration strategy should be in uenced by the number and complexity of the changes you need to make to your application to have it function properly on MPE/iX-based systems. Also, you should note the changes which are necessary to run in CM or NM, as this, too, in uences your migration strategy. A thorough understanding of the application may be necessary to assess the impact of the incompatibility.
Severity of Incompatibilities Once you have determined what potential incompatibilities exist in your application, you need to determine how your application depends on the item in question. In some cases, what is agged as an incompatibility may not cause your application to run incorrectly but it is something that you should investigate to determine the impact on your application.
How the application uses MPE intrinsics. How the application accesses data. Whether or not the application encounters storage or performance limits. Whether or not the application interfaces with another application. What related applications are being migrated. What the application's MPE/iX disk space requirements are when migrated to an MPE/iX-based system. Migration Goals After analyzing the incompatibilities and characteristics of the application, you need to establish migration goals.
What data format is required? Is all required Hewlett-Packard or third party software (or equivalent) available for use on the MPE/iX-based system? Do you need to share les with MPE V/E systems in a network? Will source and program les be sharable across both MPE V/E-based machines and MPE/iX-based machines? Time and Resources Once you have established the migration goals, you will need to determine what time and resources you need to commit to completing those goals.
Migration strategy Migration schedule Resource requirements Documentation and training requirements Detailed application analysis Test plan Purpose and Scope The scope should include all areas addressed by the plan. The purpose is a statement of how you will use the migration plan. Project Identification Project identi cation includes both customer and application identi cation. Application identi cation is a brief description of the application covered by this migration plan.
migration strategy will be slightly more complex. You may need diferent migration strategies for di erent applications. Hewlett-Packard gives you exibility; you decide which migration options to choose for your applications. A migration goal is a statement describing the functionality and performance expectations, as well as a timeframe for completion. The target state describes the operating mode and options for all programs and databases that make up the application.
Hardware requirements list the 900 Series, disk drives, tape drives, printers, terminals, and any other hardware needed for migration. Software requirements list MPE/iX with version number, compilers, subsystems, tools, database management systems, and any other software needed for this project. Documentation and Training Requirements Documentation and training requirements should list the training and documentation needs for all personnel involved in the migration project.
third party software. contributed library dependencies. known incompatibilities. potential problem areas. list of intrinsics and external references. A procedure owchart or call map can be very useful in describing the application. Reports from the Migration Toolset (MPT, OCA, and RTM) should be included here. Test Plan This is the eighth and last section of your migration plan. The test plan should include the test data and procedures that will be used at each stage of the migration.
4 Preparation Preparation readies the existing MPE V/E system for migration. Software updates can be done before the 900 Series hardware arrives. This involves updating to U-MIT or later software, including databases, data communications, and languages. Compiler Conversions Most MPE V/E applications will run in CM on MPE/iX without recompilation. Simply restoring the application onto an MPE /iX-based system enables you to immediately execute the application in CM.
review the appropriate language migration guide (listed under \Documentation and Training" in Chapter 1, \Introduction and Migration Overview"). Subsystem Changes Application Changes Convert all databases to TurboIMAGE before migrating to the 900 Series HP 3000. Convert from DS/3000 to NS3000. NS3000/XL is the data communications system for the 900 Series HP 3000.
Preparing the HP 3000 MPE V/E System for Migration Accounting Structure User-Logging ID Table DIRMIG allows the system manager to duplicate the MPE V/E operating environment on the MPE/iX system. The operating environment consists of account structure information, including the UDC environment, private volume information, and system tables information. DIRMIG runs on your MPE/iX-based system and takes as input your MPE V/E SYSDUMP tape.
UDCs and User Files Disable any system-level, account-level, and user-level UDCs that users do not want to migrate. Run the GETUDC utility on the resultant MPE V/E system. GETUDC aids in the migration of the MPE V/E UDC environment by creating a text le containing the names of all system-recognized UDC les. Refer to Appendix F, \Using the GETUDC Utility" for details on using GETUDC.
Preparing to Perform Migration Ensure that all necessary components are available before continuing. A Hewlett-Packard representative should have installed and con gured the 900 Series HP 3000. Check to be sure that the system is up and loaded. Note Software Requirements Please refer to the HP 3000 Computer Systems System Con guration Guide (5954-9354) for current information on supported peripherals.
5 System Installation During System Installation, the migration team completes the installation, initial system test, and con guration of the 900 Series HP 3000. The team uses DIRMIG.PUB.SYS to migrate most of the MPE V/E operating environment to MPE/iX. Tasks performed during the installation stage include: Installing MPE/iX (System Startup Con guration and Shutdown (32650-90034)). Con guring the MPE/iX system (System Con guration (32650-90042) ). Completing System Migration (Appendix G of this manual).
Directory Migration Tool (DIRMIG) DIRMIG migrates the MPE V/E operating environment to MPE/iX. The operating environment includes: System tables information Global Resource Identi cation Numbers (RINs) User-logging identi ers Directory structure/user les UDC environment Private volume information DIRMIG uses an MPE V/E SYSDUMP tape as input.
logging facility records the migration status of each component and provides detailed information in the event that any errors occur. To assist with private volume migration, DIRMIG creates three other les: PVASSIST.PUB.SYS, PVSUMARY.PUB.SYS, and VOLUTIL command les as speci ed by the user. PVASSIST contains private volume information for the accounts DIRMIG migrates.
Complete migration with no dialog Complete migration with dialog Migration of global RINs Migration of user-logging IDs Directory migration Private volume environment migration The dialog option of complete migration displays more detailed menus at each step of the process. These detailed menus allow the user to continue without migrating a particular component, to display information from the MPE V/E SYSDUMP tape, and to use the HELP feature.
6 Compatibility Mode Operation This is the fth stage of migration. The objective of this stage is to ensure that programs that run successfully on MPE V/E-based HP 3000 systems also run successfully on MPE/iX-based HP 3000 systems in CM. The result of this stage is a set of CM applications whose results have been validated with the original versions. Activities of this stage include: Completing the changes identi ed in the analysis and planning stage necessary for operation in CM.
NM procedures can be called through the Switch subsystem. For more information on the Switch subsystem, refer to the Switch Programming Programmer's Guide (32650-90014). If recompiling is necessary for CM operation, you should use one of the MPE V/E compilers available in CM on MPE/iX and the MPE V Segmenter if necessary. Program Validation Improving Performance A complete CM test plan should be part of your migration plan.
only selected segments of the object code, or add translated segments to another le. Object code translation will increase the size of the le.
A Maintaining Backward Compatibility This appendix describes how to maintain backward compatibility for programs and les. It is especially useful for developing programs on an MPE/iX-based system that may be transported to an MPE V/E-based system. How to Ensure Compatibility Programs can be developed in CM on MPE/iX for use on MPE V/E-based systems. It is important to understand that you are basically working in the MPE V/E environment when you are in CM.
Use compatible database products. Additional information on these guidelines can be found in the Introduction to MPE XL for MPE V Programmers (30367-90005) or the appropriate language or subsystem guide. When changes are made to an MPE/iX CM program, the same changes should be made to the MPE V/E program, and both programs should be validated for consistency and accuracy. Unavoidable Problems A-2 There are certain di erences between MPE V/E and MPE/iX that are unavoidable.
B Using the Object Code Analyzer This appendix describes how to use OCA (Version A.00.05). The OCA is intended to be used in conjunction with its companion Migration Toolset utilities, MPT and RTM, during the analysis and planning stage of the migration e ort. OCA runs on both MPE V/E-based and MPE/iX-based systems. Included in this appendix are discussions on the following subjects: \OCA Operation", a general overview of how the tool operates. \Using OCA", a detailed description of the user interface.
OCA Operation OCA is a tool designed to aid in migrating applications from an MPE V/E-based system to an MPE/iX-based system. OCA is a dialog-driven program that scans speci ed MPE V/E program and SL les in either batch or interactive mode and generates either brief or detailed reports of both de nite and potential problem areas that may be encountered when migrating an application to an MPE/iX-based system.
referenced procedures that have been identi ed as incompatibilities for the purposes of migration. Use the brief report format if you are interested primarily in a migration report. Appendix D, \Incompatibilities", gives greater detail on each of the incompatibilities detected by OCA, as well as corrective actions to take. When you specify a detailed report format, OCA reports on all of the program le's externally referenced procedures, as well as general information about the program's structure.
Using OCA OCA is initiated by running the program le OCA.PUB.SYS either interactively or in batch mode. You can get an explanation of the input expected for any particular prompt by entering a question mark (?). You may also issue any MPE command that can be executed programmatically by pre xing it with a colon (:). After the HELP text is displayed, or the MPE command is executed, the original prompt is redisplayed. A double slash (//) at any prompt causes OCA to terminate.
Figure B-1.
Enable Options Prompt Do you want to enable any options (yes/NO)? This is the rst prompt from OCA. You are being asked if you wish to access the two optional features of OCA prior to entering the scanning portion of the program. A positive response takes you to the User Externals prompt. A negative response (the default) or a 4Return5 A \//" terminates OCA.
then two di erent messages may be reported. OCA prints a message if you add an external procedure name already in the list. Enter External Prompt Enter external procedure name or indirect file name: You are being prompted for the external procedures that you want added to the events detected by OCA. You can specify system entry points and user-written procedures.
Because of restrictions in the MPE V Segmenter and the program/SL le format, procedure names are truncated to 15 characters. OCA follows this convention and issues a warning message when a name is over 15 characters in length. External procedure names can be quoted (with either single or double quotes) or unquoted: Unquoted procedure names are upshifted as is the usual convention on an MPE V/E-based system. Quoted procedure names are treated as literals and are not upshifted or downshifted.
The general format of this le is similar to the format of indirect les described later in this appendix, except that nested indirect les are not allowed at this prompt. The le should contain one procedure name per line (leading and trailing blanks are ignored). The conventions for specifying external procedures are described in \External Procedure Names" above. You can use the string \|" to delineate the rest of the line as a comment that is ignored by OCA. The end of line ends the comment.
A \//" terminates OCA. This \Build Indirect File" feature can be useful if you have a large number of les to scan that are centralized in a few key groups and accounts on the system, and you want to save the set of le names for future use. A second use of this feature is generating a list of the names of programs and SL les to be considered as candidates for migration.
Indirect File Name Prompt Enter name for indirect file: You are being prompted for the name of the le you want to associate with the indirect le you are about to create. This le will contain the names of les that you later want OCA to scan during the scanning portion of the program. Valid responses to this prompt are: A le name following MPE V/E le naming conventions. A 4Return5 takes you to the Scan prompt. A \//" terminates OCA.
OCA attempts to close the indirect le as a permanent le. If a le of the same name already exists in the permanent le directory, OCA asks you if the old le should be purged. If you respond YES, OCA purges the old le before it closes the indirect le. If you respond NO to the purge request (or press 4Return5), OCA asks if you want to save the le under a di erent name. If you respond NO to this prompt (or press 4Return5), the indirect le you just built is lost.
In both cases where the le is lost, OCA returns you to the Indirect File Name prompt and allows you to create a new indirect le. When you succeed at saving the indirect le, OCA takes you to the SCAN prompt.
Details of the le speci cation , library speci cation , report level , and report destination parameters are discussed below. File Specifications OCA scans only MPE V/E format SL or program les.
By File Name. You can enter the name of a single program or SL le. OCA displays an error message if the le is not of the correct type. Program and SL les are treated slightly di erently; the di erences are re ected only in the detailed report. By File Set. You can enter a le set. You can select groups of program and/or SL les using MPE wild card characters (@ , # , ? ) in conjunction with le designators.
ASCII Permanent, existing in the system le domain File code must be 0 (the default) If you respond with an incorrect or nonexistent le name, OCA produces an error message and issues the prompt again. The general format of this le is similar to the format of indirect les described earlier in this appendix, except that indirect les of le speci cations can be nested up to ve levels deep. The le should contain one command per line (following the syntax described above). Leading and trailing blanks are ignored.
LIB= Option The LIB= option tells OCA what system libraries the loader would search if the speci ed program le were to be loaded. It is interpreted in exactly the same way as the LIB= option on the MPE V/E :RUN command. The default library indicator is \S". Specifying LIB=S is equivalent to omitting the LIB= option entirely. The LIB= option should be speci ed only with program les. If you specify LIB with an SL le, the LIB= parameter is ignored.
Brief and Detailed Options By default, OCA produces a report on le speci cation in a brief format that provides only information directly related to migrating the program le successfully, including names of external procedures that have been identi ed as incompatibilities for the purposes of migration. Specifying ;BRIEF with a le name or le set is the same as not specifying ;BRIEF.
SCAN Prompt SCAN> You are being prompted for the name of the le(s) you want OCA to scan for incompatibilities. Valid responses to this prompt are: A le speci cation (with optional keyword parameters), following the syntax description described below. 4Return5, which returns you to the SCAN prompt. A \//", which terminates OCA. A report is generated for each le scanned, and you are prompted for the name of the next le to scan.
le speci cation [library speci cation] [report level] [report destination]'' The syntax for the required le speci cation is: { { { { filename } fileset } !indirect filename #indirect filename The syntax for the optional library speci cation is: { GROUP } [; LIB = { PUBLIC } ] { SYSTEM } B-20 Using the Object Code Analyzer } }
The syntax for the optional report level is: [; DETAILED ] [; BRIEF ] The syntax for the optional report destination is: [; OFFLINE ] As a convention, OCA keywords are shown in upper case, although you do not have to enter them in upper case on the command line. In addition, only the minimum number of characters necessary to recognize the keyword must be speci ed. For example, ;DETAILED can be entered as ;DET or as ;D.
By File Set. You can enter a le set by selecting groups of program and/or SL les using MPE wild card characters (@, #, ?) in conjunction with le designators. OCA searches the speci ed le set and scans only the program and SL les located in the speci ed le set. For example, if you specify @.mygroup.myacct, OCA scans all program and SL les located in group mygroup, account myacct.
By Indirect File Name. You can enter the name of an indirect le that you have previously created either by the Build Indirect File option of OCA or from an editor. As is the case with all OCA indirect les, the le name must be preceded by either a ! or a %.
The general format of this le is similar to the format of indirect les described earlier in this appendix. Indirect les of le speci cations can be nested up to ve levels deep. The le should contain one le speci cation per line (following the syntax described above). Leading and trailing blanks are ignored. You can use the string \| " to delineate the rest of the line as a comment that is ignored by OCA. The end of line ends the comment. Blank lines are likewise ignored.
default library indicator is \S". Specifying LIB=S is equivalent to omitting the LIB= parameter. The LIB= option should be used only if scanning a program le. If you specify LIB= with an SL le, the LIB= parameter is ignored. When the LIB= option is used with either a le set or an indirect le, the speci ed library is applied to those les in the le set (or in the indirect le) that are program les, and ignored for the SL les.
of migration Specifying ;BRIEF with a le name or le set is the same as not specifying ;BRIEF. You can optionally specify ;DETAILED if you want much greater detail about all of le speci cation's externally referenced procedures. In addition, the ;DETAILED option produces general information about the program structure of le speci cation . Specifying either the ;BRIEF or the ;DETAILED option with an indirect le overrides all uses of this option that may be found within that indirect le.
YES (the default) tells OCA that you want to continue listing the text. OCA will display the More prompt each time it lls one page on your screen. NO tells OCA that you do not want to see the rest of the text. OCA stops scanning any other les speci ed, and returns you to the SCAN prompt. ALL tells OCA that you want to see all of the report without intervening More prompts. OCA uses two session level job control words (JCWs) to control page length for output (help text or reports).
Security Considerations Running OCA in Batch Mode B-28 There are no special restrictions on who can run OCA. OCA, however, places restrictions on which les may be scanned. You must have READ access to the le to scan it. In addition, you must provide lockwords for les requiring them. Users possessing Account Manager capability may scan any le residing in their accounts without specifying the lockword.
:job ocajob, manager.sys :run oca.pub.sys y y procedure1 procedure2 procedure3 procedure4 procedure5 ------ want to enable some options want to add user selected externals enter the names of some procedures you want to add to predefined list of system incompatibilities -- blank line indicates no more procedure names :comment save the procedure names entered above for later use :save ocapname y -- want to build an indirect file indirect -- call the file indirect @.@.
OCA Report Formats A report is automatically generated for each le that OCA scans. There are two formats of the report: Brief format Detailed format The brief report format provides only information directly related to the ability of the program or SL le to migrate successfully. This information includes a list of potential incompatibilities detected when OCA scanned the selected program or SL les.
Use an editor to nd the exact location in your source le of the call to the incompatible procedure. Use the compiler listing and a cross reference to nd the exact location of the call to the incompatible procedure. Output Device Specification If you use the ;OFFLINE option, you can direct OCA report or HELP text output to the OCA list le OCALIST. By default this le is assigned to the system line printer (DEV=LP).
Resolved External Procedures Unresolved External Procedures (returned for program les only) Potential Incompatibilities Intrinsic Mechanism Information General Information Table B-1 summarizes the information returned in the \General Information" section of an OCA report. This information is returned only for program les; segmented library (SL) les do not have equivalent characteristics. The rst two categories of information indicate potential migration issues.
Table B-1.
Table B-2.
large programs and for programs that use SL les. Hewlett-Packard recommends that you request this information only if you need to get a \feel" for what a program is doing, and how it does it (for example, if you are migrating a program you did not write). Table B-3.
Table B-4. Unresolved External Procedures (program files only) Information Brief Detailed A list of the external procedures which were unresolved X X The reason why the procedure was unresolved X X Potential Incompatibilities Table B-5 summarizes the information returned in the \Potential Incompatibilities" section of an OCA report. This section lists the potential migration issues you should expect to encounter.
entry in an SL segment (whether directly or indirectly), OCA scans all procedures found in the SL segment, whether or not they are actually referenced. This occurs because the whole SL segment (not just the referenced procedures) is bound to the program at run time. The recommended method of determining whether or not a reported procedure is actually called by a program is to enable RTM and run the program again. (For details on this method, refer to Appendix C, \Using the Run Time Monitor".) Table B-5.
procedures and determine whether the procedures are actually referred to. Summary Information Table B-6 summarizes the information returned in the \Summary Information" section of an OCA report. This section reports total numbers of events listed in the \Potential Incompatibilities" section of the report. Table B-6.
Table B-7. Intrinsic Mechanism Information Information Brief Detailed A message brie y explaining the intrinsic mechanism issue X X A list of all the intrinsics that the application references X X Although you may not recognize it by the name intrinsic mechanism, the intrinsic mechanism has been an MPE V/E feature for a long time.
If you plan to migrate your application to NM on MPE/iX, you must use the intrinsic mechanism to get correct results. By mandating the use of the intrinsic mechanism and enhancing it to contain several new features, MPE/iX will be able to provide a programmatic interface which is more exible and extensible than the one currently provided by MPE V/E. Each of the MPE V/E programming language reference manuals contain a section on how to call system intrinsics.
cannot nd references to in your source code fall into this category. When you recompile your source code on MPE/iX using NM compilers, all compiler-generated external references are handled through the intrinsic mechanism. Sample Brief Report Figure B-3 provides a sample of a brief OCA report.
OCA HP30365A.00.05 (Cat A.00.05) - THU, OCT 23, 1986, 11:01 AM Page No. 1 Report for STICP.SOOL.MPEV ;LIB=G ;BRIEF G E N E R A L I N F O R M A T I O N Program was prepped with ;CAPS=BA,IA. Program contains only user mode segments. P O T E N T I A L I N C O M P A T I B I L I T I E S Incompatibilities detected in the program file "STICP.SOOL.MPEV". FCONTROL: *** System Defined Incompatibility *** - Some FCONTROL controlcodes are no longer valid on MPE/iX (CM/NM 500). These control codes include: 03, 48.
Sample Detailed Report Figure B-4 provides a multipage sample of a detailed OCA report. It provides an expanded listing of general information, segment information, and resolved external procedures.
OCA HP30365A.00.05 (Cat A.00.05) - THU, OCT 23, 1986, 11:01 AM Page No. 1 Report for STICP.SOOL.MPEV ;LIB=G ;DETAILED G E N E R A L I N F O R M A T I O N Program was prepped with ;CAPS=BA,IA. Program contains only user mode segments. Program was prepped with ;CAPS=BA,IA. Program contains only user mode segments.
R E S O L V E D E X T E R N A L P R O C E D U R E S External references of the program "STICP.SOOL.MPEV".
Called At Resolved To ---------------------------Procedure Name Seg Num STT Num LIB ===================================================== P'RESET %00000 3 SYSTEM %000052 **** O F F S E T S **** Total Number of calls in segment 0: 1 Total number of calls to P'RESET: 1 Number of segments which call P'RESET: 1 Called At Resolved To ---------------------------Procedure Name Seg Num STT Num LIB ===================================================== P'REWRITE %00000 4 SYSTEM %000035 **** O F F S E T S **** Tot
**** O F F S E T S **** %000073 Total Number of calls in segment 0: 1 Total number of calls to TERMINATE': 1 Number of segments which call TERMINATE': 1 External references inherited from the group SL (SL.SOOL.MPEV).
Incompatibilities detected in the group SL (SL.SOOL.MPEV). CREATEPROCESS: *** System Defined Incompatibility *** - CREATPROCESS may encounter byte pointer problems in NM on MPE/iX (NM 107). FCONTROL: *** System Defined Incompatibility *** - Some FCONTROL controlcodes are no longer valid on MPE/iX (CM/NM 500 These controlcodes include: 03,48.
OCA Program Error Messages User Input Errors There are two classes of program error messages generated by OCA: User input errors that cause syntax and semantic errors Internal error messages OCA generates and displays to $STDLIST error messages for any syntax and semantic errors associated with user input. OCA follows these guidelines when generating this class of error messages: Displays le system error messages. Echoes user input. Attempts to point to the error with a carat (^).
d c SCAN> ! IFILE;LIB=G -- read from IFILE.PUB.PERS BADFILE;;LIB; ^1 ^2,3 ^4,5 ERROR 1: Missing option. Expected one of LIB, BRIEF, or DETAILED (IFILE.PUB.PERS) ERROR 2: Missing = after LIB (IFILE.PUB.PERS) ERROR 3: Missing G, P, or S after = (IFILE.PUB.PERS) ERROR 4: Missing option. Expecting one of LIB, BRIEF, or DETAILED (IFILE.PUB.PERS) ERROR 5: Extraneous input after command (IFILE.PUB.PERS) SCAN>NOTFILE NONEXISTENT PERMANENT FILE (FSERR 52) NOTFILE ^1 ERROR 1: Unable to open NOTFILE.PUB.
101 102 MESSAGE INTERNAL ERROR 101: CATREAD failed in REPORT. Display of message with NLS failed. Msg_num = nnn Set_num = nnn CATREAD error = nnn CAUSE Attempting to display a message from the catalog le via the REPORT procedure. CATREAD failed for some reason. Possible causes of the CATREAD failure are explained in the MPE V/E Native Language Support Reference Manual (32414-190001). ACTION This error is likely to occur if the OCA catalog has been incorrectly localized.
103 MESSAGE INTERNAL ERROR 103: CATREAD failed during NLDISPLAY. Display of message with NLS failed. Msg_num=nnn Set_num=nnn CATREAD error=nnn CAUSE Attempting to display a message from the catalog le via the NLDISPLAY procedure. CATREAD failed for some reason. Possible causes of the CATREAD failure are explained in the MPE V/E Native Language Support Reference Manual (32414-90001). 104 B-52 ACTION This error is likely to occur if the OCA catalog has been incorrectly localized.
105 MESSAGE INTERNAL ERROR 105: Unable to retrieve localized string from OCCATnnn .PUB.SYS. CATREAD error nnn OCA cannot continue. (or) String read from catalog is too long. (MAX=nnn Chars.) String: the actual string read from catalog(nnn) 106 107 CAUSE Attempting to CATREAD a localizable string from the OCA catalog, a problem is encountered.
108 109 110 B-54 MESSAGE INTERNAL ERROR 108: Cannot Obtain NLDOWNSHIFT Table For Language nnn . NLINFO Error nnn during SETUP. CAUSE NLS intrinsic NLINFO returned an error when the DOWNSHIFT table for language nnn was requested. Possible causes of the NLINFO failure are explained in the MPE V/E Native Language Support Reference Manual (32414-90001).
111 MESSAGE INTERNAL ERROR 111: CATOPEN Error nnn . Unable To Open Catalog File OCCATnnn .PUB.SYS. OCA Cannot Continue. CAUSE CATOPEN intrinsic returned error nnn when attempting to open the OCA catalog le. Possible causes of the CATOPEN failure are explained in the MPE V/E Native Language Support Reference Manual (32414-90001). ACTION 200 to 299 MESSAGE 300 301 Make sure the catalog le mentioned in the message exists in the correct group and account, and has the current le code (MGCAT).
302 303 304 MESSAGE INTERNAL ERROR 302: Bad keyword index. CAUSE Attempting to access an entry in one of OCAs internal keyword tables using an invalid index. ACTION Contact a Hewlett-Packard Support Representative. Include all information printed by OCA when it aborted. MESSAGE INTERNAL ERROR 303: SL directory entry points to deleted segment. Bad SL file, n 1, detected. CAUSE OCA has determined that the directory contained in the SL le it scanned is corrupted.
305 306 307 MESSAGE INTERNAL ERROR 305: FREADDIR intrinsic failed. CAUSE The most likely cause of this problem is either program or SL le corruption (of the program or SL le being scanned, not of the OCA program le). If you are scanning a program le when you get this error, you can double check to see if it is corrupt by attempting to :RUN the program. If it is corrupted, the MPE loader will probably print a similar message to the one printed by OCA.
C Using the Run Time Monitor This appendix describes how to use RTM (Version A.00.01). RTM is intended to be used in conjunction with its companion Migration Toolset utilities, MPT and OCA, during the analysis and planning stage of the migration e ort. RTM runs on MPE V/E-based systems. Included in this appendix are discussions on the following subjects: \Run Time Monitor Operation", a general overview on how the tool operates. \Setting up Run Time Monitor", how to install RTM on your MPE V/E-based system.
Run Time Monitor Operation RTM is a tool designed to aid in migrating applications from an MPE V/E-based system to an MPE/iX-based system. The task of RTM is to monitor executing applications for occurrences of prede ned events. An event is de ned as an MPE V/E intrinsic feature that will be incompatible when executed on an MPE/iX-based system. RTM is made up of three parts: A controlling program, RTMSYS.PUB.SYS, used to enable RTM and to specify the event classes to monitor. A report program, RTMREP.PUB.
Table C-1. Run Time Monitor Event Classes Class Number Class Name Description 0 Logging Enabled Enable/disable RTM operation 1 NM Events Enable disable logging of uniquely NM events (in addition to events common to both CM and NM. 2 Enable/disable logging of any Command Intrinsic Events incompatible command executed by the COMMAND intrinsic. Commands are not associated with a speci c mode. Therefore, the NM Events (class 1) does not e ect this event class.
RTMREP A report of events can be generated by using the RTMREP program. RTMREP reads the speci ed system log les and generates a report to the formal le designator RTMLIST of the events found. Two report formats are available: A brief report (the default) is a program summary which shows the events generated by each program. A counter shows the number of times that a particular call caused the event. The report is sorted by date, program name, and event class.
Managing Run Time Monitor Stack Space Usage When RTM is enabled, your programs will use slightly more stack space. The amount of additional stack depends on the intrinsics called by your program. Intrinsics with more parameters will incur more stack overhead when RTM is enabled. The additional stack overhead ranges from 8 to 60 words. Your applications will use more stack from the time the intrinsic is called until control is returned to your program.
incur any overhead due to RTM. Unfortunately, RTM will not be able to monitor these programs so you will need to rely on OCA for your migration information. Managing Run Time Monitor Disk Space Usage RTM uses the MPE V/E System Logging facility to keep track of migration events as they occur on your system. As log le records are generated, RTM will consume disk space on your system. The rate of consumption varies based on several di erent factors.
d a :LISTF LOG####,PUB,SYS,2 ACCOUNT= SYS GROUP= PUB FILENAME CODE LOG1327 LOG1328 LOG1329 c LOGICAL RECORD SIZE TYP EOF 1022W VB 1022W VB 1022W VB 27165 13012 5402 LIMIT R/B 1023 1023 1023 1 1 1 SPACE SECTORS #X MX 8192 4096 2048 16 16 8 16 4 16 b By totaling the SECTORS column you can determine how much disk space is being consumed by the system log les (in the example above, 14,336 sectors have been used).
Setting Up Run Time Monitor Note Caution System logging and the program le event (type 16) must be enabled through the MPE V/E SYSDUMP facility for RTM to work. (Refer to the MPE V/E System Operation and Resource Management Manual (32033-90005) for details on enabling system logging and the program le event.) Since any program already loaded or allocated is not linked through RTMSL.PUB.
Operator Logon UDC The rst method you can use to automatically enable RTM is to have OPERATOR.SYS execute a logon UDC that runs the RTMSYS program with an info string. The info string contains the name of a le that has the event classes turned on or o , as desired. Each entry in the le looks exactly as if it was typed interactively. ****** EVENTUDC OPTION LOGON : RUN RTMSYS.PUB.SYS;info="RTEVENTS.PUB.SYS" ****** The le RTEVENTS.PUB.
Using RTMSYS RTM is controlled by the program RTMSYS. RTMSYS can be run interactively or in batch mode by any user possessing OP or SM capability by entering: : RUN RTMSYS.PUB.SYS You only need to run RTMSYS to change the status of an event class. Figure C-1 charts the ow of control with RTMSYS prompts. Additional information on the prompts is provided in subsequent headings. Defaults for all prompts are shown in upper case.
Using the Run Time Monitor Figure C-1.
Status Changes Prompt RTMSYS initially displays all event classes and their current status. The rst prompt asks you if you want to make changes to the classes of events that RTM detects: A positive response causes RTMSYS to continue and takes you to the command le prompt. A negative response, or 4Return5, terminates RTMSYS d a HP30364A.00.00 Run Time Monitor (C) HEWLETT PACKARD COMPANY 1986 Enter a question mark (?) at any prompt for help. Default answers are shown in upper case.
A positive response takes you to the Enter Command File prompt. A negative response (the default), takes you to the Enter Class prompt.
Enter name of command file: Enter Command File Prompt At this prompt, you should enter the name of the command le. Valid responses include any valid le name of a le containing the event classes and desired status. This le can be any standard, EDIT/3000 compatible le, either numbered or unnumbered, that contains records indicating the class number and desired status. Each line contains a class number and the desired status for that particular class.
:job rtmstart, manager.sys, pub :comment :comment check to see if rtmstart.pub.sys exists :comment :setjcw cierror=O :listf rtmstart.pub.sys :comment :comment if rtmstart.pub.sys does not exist then create it :comment :if cierror = 907 then :editor a 0,on 1,on 2,on 3,on 4,on 5,on 6,on 7,on 8,on // k rtmstart.pub.sys e :endif :comment :comment run rtmsys.pub.sys with command file created above :comment :run rtmsys.pub.sys;info="rtmstart.pub.sys" :eoj Figure C-2.
:job rtmstop, manager.sys, pub :comment :comment check to see if rtmstart.pub.sys exists :comment :setjcw cierror=0 :listf rtmstop.pub.sys :comment :comment if rtmstop.pub.sys does not exist then create it :comment :if cierror = 907 then :editor a 0,off 1,off 2,off 3,off 4,off 5,off 6,off 7,off 8,off // k rtmstop.pub.sys e :endif :comment :comment run rtmsys.pub.sys with command file created above :comment :run rtmsys.pub.sys;info="rtmstop.pub.sys" :eoj Figure C-3.
:job rtmrep, manager.sys, pub :comment :comment The responses to the RTM prompts below have the :comment following meanings: :comment :comment Response Meaning :comment :comment :file rtmlist;dev=epoc redirect the report to the :comment epoc printer. :comment n do not want a detail line for :comment each incompatibility detected :comment 1300 start with log file 1300 :comment 1305 end with log file 1305 :comment y subset the data :comment @.@.
Using RTMREP RTM does not automatically generate reports. However, all run-time events that are captured are recorded in a system log le. A report of events logged can be generated by running RTMREP. Descriptions of the events logged by RTMSYS are found in Appendix D, \Incompatibilities". There are two report formats. A program summary (the default), a brief report that shows all events generated by each program. A counter shows the number of times that a particular segment/o set caused the event.
You may also issue any MPE V/E command that can be executed programmatically be pre xing it with a colon (:). Output Device Specification The output formal le designator is RTMLIST, which by default is opened with device class LP. The :FILE command can be used to redirect the output as necessary. Figure C-5 charts the ow of control with RTMREP prompts. The prompts are described under the following headings. Defaults for all prompts are shown in upper case.
C-20 Figure C-5.
Detail Line Prompt HP30364A.00.00 Run Time Monitor (C) HEWLETT PACKARD COMPANY 1986 Enter a question mark (?) at any prompt for help. Default answers for all prompts are shown in upper case. Do you want a detail line for each event [yes/NO]? A positive answer to this prompt gives you the detailed report. A negative answer (the default) to this prompt gives you the summary report. Either response takes you to the Log File Speci cation prompts.
A negative response (the default) reports on all available information. Enter Program File Subset Prompt Enter program file subset [CR will select all]: You are being prompted for the name of a le(s) you want RTMREP to create a report about. In addition, you can specify a set of program les using wild card characters (@, #, ?) in conjunction with MPE V/E le speci cations. For example, the following le set speci cation indicates all program les that start with the letter \C": C@.MYGROUP.
1HP30364X.01.02 0PROGRAM FILE STICP.SOOL.
Run Time Monitor Program Error Messages C-24 The following list of error and warning messages are generated by the two programs that make up the RTM utility, RTMSYS and RTMREP.
12 14 31 39 MESSAGE Classes must be numeric in the range 1..8 CAUSE In RTMREP you have selected a subset class that was either not a numeric value or was beyond the speci ed range (1 . . . 8) ACTION Respecify the selection you want: The correct syntax is discussed under \Enter Class Numbers Prompt". MESSAGE Is incomplete - a maximum of 100000 records per run allowed . CAUSE In any single run of RTMREP, the program can only sort 100,000 records of selected migration events.
41 42 43 44 45 MESSAGE Input must be in the form: "1, ON" or "1, OFF". CAUSE RTMSYS was expecting to nd a comma between the two tokens you provided. ACTION Respecify your input with a comma between the event class and the requested status (ON or OFF). The correct syntax is discussed under \Enter Class Prompt". MESSAGE Class must be numeric, for example "1,ON". CAUSE RTMSYS found that the rst token you speci ed was not a numeric character.
46 48 49 54 55 MESSAGE WARNING Logging class 16 is disabled - use SYSDUMP to enable it. CAUSE Refer to Cause of Error Message 45. ACTION Refer to Action of Error Message 45. MESSAGE The VUFs of RTM segments in SL.PUB.SYS and RTMSL.PUB.SYS do not match. CAUSE RTMSYS has done internal checking of the modules necessary to run event logging. RTMSYS has discovered an inconsistency between these modules. ACTION RTM may not be correctly installed on your system.
D Incompatibilities This appendix lists all known incompatibilities between MPE V/E and MPE/iX. These incompatibilities are divided into two categories, undetected incompatibilities and detected incompatibilities. Undetected Incompatibilities Peripheral Dependent Incompatibilities Incompatibilities that cannot be detected by the Migration Toolset (MPT, OCA, and RTM) are considered undetected incompatibilities.
FREADBACKWARD will result in a run-time error, since no tape drives with reverse read capability are supported on MPE/iX. FWRITE controlcodes %311, %312, %313, %314-317 are associated with devices that are not currently supported on MPE/iX.
Various MPE/iX subsystems require le numbers for their own use. Therefore, you should make no assumptions about le numbers returned to your program. All hardcoded le numbers should be removed and replaced with appropriate variables that contain the le number values returned by system intrinsics. Intrinsic parameter types and conventions have changed in NM. You should use the intrinsic mechanism to ensure compatibility.
Command Incompatibilities The Migration Toolset does not search for all command incompatibilities. Refer to the MPE V to MPE XL: Getting Started Self-Paced Training (30367-90002) and Introduction to MPE XL for MPE V System Administrators (30367-90003) for descriptions of the command changes from MPE V to MPE/iX. Note whether the iX command changes will a ect current programs or UDCs and make the necessary changes.
Subsystem and Compiler Incompatibilities This section summarizes non-Operating System speci c incompatibilities. For more information, refer to the appropriate migration guide.
Introduction to MPE XL for MPE V Programmers (30367-90005). SPL is available in CM both for run-time support and for development of SPL applications. Your SPL applications and SPL procedures will run in CM. However, because of its close relationship to the MPE V/E-based architecture, Hewlett-Packard does not support a NM SPL compiler on the 900 Series. The OCT can be used to increase the performance of MPE V/E object code.
problems on MPE V/E-based systems may cause programs to abort on MPE/iX-based systems. System Logging Incompatibilities Detected Incompatibilities Note The formats and record types of system log les have been modi ed. If a program processes records from a system log le, the program must be changed to specify the appropriate iX record types. Refer to Getting System Information Programmer's Guide (32650-90018) for a listing of the new record types and formats for the iX system log les.
You can nd further information about di erences between MPE V/E and MPE/iX in the Introduction to MPE XL for MPE V Programmers (30367-90005), where potential incompatibilities associated with system intrinsics are described in greater detail than in this appendix. 101 MESSAGE MODE CAUSE ACTION 102 MESSAGE MODE CAUSE ACTION D-8 Incompatibilities XARITRAP intrinsic may require a new trap handler in MPE/iX NM. NM incompatibility detected by MPT (severity level WARNING), OCA, and RTM (Event Class 1).
103 MESSAGE MODE CAUSE ACTION 104 MESSAGE MODE CAUSE ACTION 105 MESSAGE MODE CAUSE ACTION iXIBTRAP intrinsic may require a new trap handler in MPE/iX NM. NM incompatibility detected by MPT (severity level WARNING), OCA, and RTM (Event Class 1). HP-PA is a 32-bit architecture, while the architecture of MPE V/E-based computer systems is a 16-bit architecture.
D-10 Incompatibilities
106 MESSAGE MODE CAUSE ACTION 107 MESSAGE MODE CAUSE ACTION 108 MESSAGE MODE CAUSE ACTION MYCOMMAND intrinsic may encounter pointer problems in MPE/iX NM. NM incompatibility detected by MPT (severity level WARNING), OCA, and RTM (Event Class 1). HP-PA is a 32-bit architecture, while the architecture of MPE V/E-based computer systems is a 16-bit architecture.
109 MESSAGE MODE CAUSE ACTION 110 MESSAGE MODE CAUSE ACTION 196 MESSAGE MODE CAUSE ACTION D-12 Incompatibilities SWITCHDB intrinsic not supported in NM. NM incompatibility detected by MPT (severity level ERROR) and OCA. The SWITCHDB intrinsic changes the DB register so that it points to the base of an extra data segment instead of the base of the stack on MPE V/E and in CM. The SWITCHDB intrinsic is not available to programs executing in NM.
Incompatibilities D-13
200 MESSAGE MODE CAUSE COMMAND intrinsic possible programmatic execution of incompatible commands. CM and NM incompatibility detected by MPT (severity level POSSIBLE) and OCA. Some MPE V/E commands have either been modi ed for use on MPE/iX or are no longer supported on MPE/iX.
Incompatibilities D-15
203 MESSAGE MODE CAUSE ACTION 204 MESSAGE MODE CAUSE ACTION 205 MESSAGE MODE CAUSE ACTION 207 MESSAGE MODE CAUSE ACTION D-16 Incompatibilities Programmatic :LISTUSER to a le. CM and NM incompatibility detected by MPT (severity level POSSIBLE) and RTM (Event Class 2). Because of enhancements to the MPE/iX operating system, output from the :LISTUSER command appears in ASCII format.
Incompatibilities D-17
208 MESSAGE MODE CAUSE ACTION 209 MESSAGE MODE CAUSE ACTION 210 MESSAGE MODE CAUSE ACTION 211 MESSAGE MODE CAUSE ACTION D-18 Incompatibilities Programmatic :SHOWCACHE. CM and NM incompatibility detected by MPT (severity level ERROR) and RTM (Event Class 2). HP-PA features include complete operating system management of all cache activities. Programmatic control of cache activities is not allowed. MPE V/E cache management commands, including the :SHOWCACHE command are not supported on MPE/iX.
Incompatibilities D-19
215 MESSAGE MODE CAUSE ACTION 216 MESSAGE MODE CAUSE ACTION 217 MESSAGE MODE CAUSE ACTION D-20 Incompatibilities Programmatic :SHOWCOM. CM and NM event detected by MPT (severity level ERROR) and RTM (Event Class 2). Modi cations have been made to the attached peripheral environment of MPE/iX; the Intelligent Network Processor (INP) and the associated :SHOWCOM command are not supported on MPE/iX. Remove all :SHOWCOM invocations and dependent code.
218 MESSAGE MODE CAUSE ACTION 250 MESSAGE MODE CAUSE ACTION Programmatic :SPEED. CM and NM event detected by MPT (severity level POSSIBLE) and RTM (Event Class 2). Modi cations have been made to the attached peripheral environment of MPE/iX; the following baud rates are not supported: 110, 150, and 600. The :SPEED command uses a baud rate. Modify only the :SPEED invocations that specify the unsupported baud rates listed above, replacing unsupported baud rates with supported baud rates.
251 MESSAGE MODE CAUSE ACTION 252 MESSAGE MODE CAUSE ACTION D-22 Incompatibilities The meaning of the value returned in param has changed for the COMMAND intrinsic. CM and NM incompatibility detected by MPT (severity level POSSIBLE) and OCA. If RTM logs event 250, event 251 may apply to the event detected by RTM. Analyze your code to determine if this is the case.
300 MESSAGE MODE CAUSE ACTION 305 MESSAGE MODE CAUSE ACTION 306 MESSAGE MODE CAUSE ACTION Some FFILEINFO intrinsic item values may not be valid on MPE/iX. CM and NM incompatibility detected by MPT (severity level POSSIBLE) and OCA. Some values returned in the optional itemvalue parameter of the FFILEINFO intrinsic either have modi ed meanings or have no meaning on an MPE iX-based computer system.
D-24 Incompatibilities
307 MESSAGE MODE CAUSE ACTION 313 MESSAGE MODE CAUSE ACTION 315 MESSAGE MODE CAUSE ACTION FFILEINFO intrinsic itemvalue 7 hardware device address. CM and NM incompatibility detected by MPT (severity level WARNING) and RTM (Event Class 3). MPE/iX does not support the DRT number/unit number hardware address. When the speci ed le is located on a disk, the value returned by itemvalue 7 always represents DRT number 8, unit number 0, meaningless values.
D-26 Incompatibilities
316 MESSAGE MODE CAUSE ACTION 319 MESSAGE MODE CAUSE ACTION 340 MESSAGE MODE CAUSE ACTION FFILEINFO intrinsic - Item 16 maximum number of extents. CM and NM incompatibility detected by MPT (severity level WARNING) and RTM (Event Class 3). On MPE/iX, the le system manages extent allocation, where variable numbers of extents, each of variable size, are allocated based on need. There is no practical limit to the number of extents for a le.
D-28 Incompatibilities
341 MESSAGE MODE CAUSE ACTION 342 MESSAGE MODE CAUSE ACTION 344 MESSAGE MODE CAUSE ACTION FFILEINFO intrinsic - Item 41 device type. CM and NM incompatibility detected by MPT (severity level WARNING) and RTM (Event Class 3). When the speci ed le is a standard disk le (as opposed to a KSAM, RIO, or CIR disk le), MPE/iX does not distinguish between the supported disk devices' device types.
D-30 Incompatibilities
347 MESSAGE MODE CAUSE ACTION 348 MESSAGE MODE CAUSE ACTION 349 MESSAGE MODE CAUSE ACTION FFILEINFO intrinsic - Item 47 DRT number. CM and NM incompatibility detected by MPT (severity level WARNING) and RTM (Event Class 3). MPE/iX does not support the DRT number/unit number hardware address. When the speci ed le is located on a disk, the value returned in itemvalue 47 of the FFILEINFO intrinsic always represents DRT number 8, a meaningless value.
D-32 Incompatibilities
400 MESSAGE MODE CAUSE ACTION 405 MESSAGE MODE CAUSE ACTION 407 MESSAGE MODE CAUSE ACTION Some FGETINFO intrinsic item values may not be valid on MPE/iX. CM and NM incompatibility detected by MPT (severity level POSSIBLE) and OCA. The values returned in the optional devtype , hdaddr , physcount , extsize , and numextents parameters of the FGETINFO intrinsic have either modi ed meanings or no meaning on an MPE/iX-based computer system.
D-34 Incompatibilities
413 MESSAGE MODE CAUSE ACTION 415 MESSAGE MODE CAUSE ACTION 416 MESSAGE MODE CAUSE ACTION FGETINFO intrinsic physcount parameter. CM and NM incompatibility detected by MPT (severity level POSSIBLE) and RTM (Event Class 4). Because of enhancements to the MPE/iX operating system, the value returned by the optional physcount parameter of the FGETINFO intrinsic is the bu ered physical count of data blocks transferred.
500 MESSAGE MODE CAUSE ACTION 503 MESSAGE MODE ACTION MESSAGE FCONTROL intrinsic controlcode 48 Enable/Disable software MODE CAUSE ACTION D-36 FCONTROL intrinsic controlcode 3 Read hardware status word. CM and NM incompatibility detected by MPT (severity level ERROR) and RTM (Event Class 5). Because of di erences between HP-PA and the architecture of MPE V/E-based computer systems, the system hardware status word returned by FCONTROL has no meaning on MPE/iX.
601 MESSAGE MODE CAUSE ACTION 602 MESSAGE MODE CAUSE ACTION 604 MESSAGE MODE CAUSE ACTION The PTAPE intrinsic is not available on MPE/iX. CM and NM incompatibility detected by MPT (severity level ERROR), OCA, and RTM (Event Class 6). Modi cations have been made to the attached peripheral environment of MPE/iX, resulting in paper tape readers being unsupported on MPE/iX-based computer systems. The PTAPE intrinsic is not supported on MPE/ iX-based computer systems.
605 MESSAGE MODE CAUSE ACTION 800 MESSAGE MODE CAUSE ACTION 801 MESSAGE MODE CAUSE ACTION D-38 Incompatibilities KSAM record-level locking not supported on MPE/iX systems. CM and NM incompatibility detected by MPT (severity level ERROR) and OCA. Because of di erences between HP-PA and the architecture of MPE V/E-based computer systems, KSAM record-level locking is not supported on MPE/iX-based computer systems. Remove all KPTR invocations and dependent code.
802 MESSAGE MODE CAUSE ACTION 803 MESSAGE MODE CAUSE ACTION 810 MESSAGE MODE CAUSE ACTION 850 MESSAGE MODE CAUSE ACTION RFA (1000 to 3000) data communication routines are not available on MPE/iX. CM and NM incompatibility detected by MPT (severity level ERROR) and OCA. Modi cations have been made to the attached peripheral environment of MPE/iX; RFA data communication routines for communicating between HP 3000 Series computer systems and HP 1000 Series computer systems are not supported on MPE/iX.
851 MESSAGE MODE CAUSE ACTION 897 MESSAGE MODE CAUSE ACTION 898 MESSAGE MODE CAUSE ACTION D-40 Incompatibilities Printer Support Package (PSP) routines are not callable from NM on MPE/iX. NM incompatibility detected by MPT (severity level WARNING) and OCA. On MPE/iX PSP routines are not directly callable from a NM program. On MPE/iX, programs accessing the PSP routines must either run in CM or use the Switch subsystem from NM to access the PSP routines. THISCPU procedure returns new values.
899 MESSAGE MODE CAUSE ACTION 2000 MESSAGE MODE CAUSE ACTION 2001 MESSAGE MODE CAUSE ACTION 2002 MESSAGE MODE CAUSE ACTION GETPRIVMODE intrinsic may access incompatible features CM and NM incompatibility detected by MPT (severity level WARNING for CM, ERROR for NM), OCA, and RTM (Event Class 8).
D-42 Incompatibilities
2003 MESSAGE MODE CAUSE ACTION 2004 MESSAGE MODE CAUSE ACTION 2005 MESSAGE MODE CAUSE ACTION 2007 MESSAGE MODE CAUSE ACTION PARTBACKUP command not supported (use :SYSGEN or :STORE instead). CM and NM incompatibility detected by MPT (severity level ERROR). The PARTBACKUP command is not supported on MPE/iX due to changes in the method for doing system backups. Remove all references to the PARTBACKUP command from the job or UDC le, replacing them with equivalent :STORE commands.
D-44 Incompatibilities
2008 MESSAGE MODE CAUSE ACTION 2009 MESSAGE MODE CAUSE ACTION 2010 MESSAGE MODE CAUSE ACTION 2011 MESSAGE MODE CAUSE ACTION :STOPCACHE command not supported. CM and NM incompatibility detected by MPT (severity level ERROR). Disk caching is part of MPE/iX Transaction Management. It is not necessary to disable it using MPE/iX commands. Remove all references to the :STOPCACHE command from the job or UDC le. :SYSDUMP command not supported (use :SYSGEN or :STORE instead).
2012 MESSAGE MODE CAUSE ACTION 2013 MESSAGE MODE CAUSE ACTION 2014 MESSAGE MODE CAUSE ACTION D-46 Incompatibilities :VINIT command not supported (use VOLUTIL instead). CM and NM incompatibility detected by MPT (severity level WARNING). The :VINIT command is not supported on MPE/iX. The VOLUTIL program performs similar functions. Modify the job or UDC le to use the VOLUTIL program instead of :VINIT. The command syntax of VOLUTIL is di erent from that of :VINIT, which may require additional changes.
2015 MESSAGE MODE CAUSE ACTION 2016 MESSAGE MODE CAUSE ACTION 2017 MESSAGE MODE CAUSE ACTION 2018 MESSAGE MODE CAUSE ACTION :LISTUSER command - output format has changed. CM and NM incompatibility detected by MPT (severity level POSSIBLE). The :LISTUSER command is valid on MPE/iX; however, the listing format is di erent from that on MPE V/E.
D-48 Incompatibilities
2019 MESSAGE MODE CAUSE ACTION 2020 MESSAGE MODE CAUSE ACTION 2021 MESSAGE MODE CAUSE ACTION 2022 MESSAGE MODE CAUSE ACTION #:RUN LISTEQ# - not supported (use :LISTEQ or :LISTFTEMP instead). CM and NM incompatibility detected by MPT (severity level WARNING). The LISTEQ5 program has been replaced by two MPE commands: :LISTEQ and :LISTFTEMP. Note that these commands are available on both MPE V/E and MPE/iX systems.
2023 MESSAGE MODE CAUSE ACTION 2024 MESSAGE MODE CAUSE ACTION 2025 MESSAGE MODE CAUSE ACTION 2026 MESSAGE MODE CAUSE ACTION D-50 Incompatibilities :RUN DPAN# - not supported (use DAT instead). CM and NM incompatibility detected by MPT (severity level WARNING). The batch type Dump Analyzer Tool (DPAN5) from MPE V/E has been replaced by an online dump analysis tool on MPE/iX. Modify the job or UDC le to use the DAT program instead of DPAN5. :RUN OPT - not supported (use SMT instead).
2029 MESSAGE MODE CAUSE This command is used by MPE/iX. Check for UDC usage. CM and NM incompatibility detected by MPT (severity level WARNING). The following are new commands available under MPE/iX. One of them was discovered in a job or UDC le.
D-52 Incompatibilities
2037 MESSAGE MODE CAUSE ACTION 2038 MESSAGE MODE CAUSE ACTION 2039 MESSAGE MODE CAUSE ACTION 2041 MESSAGE MODE CAUSE ACTION :LISTFTEMP command - output format has changed. CM and NM incompatibility detected by MPT (severity level POSSIBLE). A job stream or UDC has invoked the :LISTFTEMP MPE command. Although :LISTFTEMP is a valid MPE/iX command, the output format for :LISTFTEMP,01 has changed.
D-54 Incompatibilities
2042 MESSAGE MODE CAUSE ACTION 2043 MESSAGE MODE CAUSE ACTION 2044 MESSAGE MODE CAUSE ACTION 2045 MESSAGE MODE CAUSE ACTION 2046 MESSAGE MODE CAUSE ACTION :GIVE command not supported. CM and NM incompatibility detected by MPT (severity level ERROR). The :GIVE command is not valid on MPE/iX. This command was used to allow certain diagnostics to access a downed device on some versions of MPE. The MPE/iX diagnostics interface does not require this functionality.
D-56 Incompatibilities
2047 MESSAGE MODE CAUSE ACTION 2048 MESSAGE MODE CAUSE ACTION 2049 MESSAGE MODE CAUSE ACTION 2050 MESSAGE MODE CAUSE ACTION 2051 MESSAGE MODE CAUSE ACTION :PURGEVSET command not supported (use VOLUTIL instead). CM and NM incompatibility detected by MPT (severity level WARNING). The :PURGEVSET command is not valid on MPE/iX. Modify the job stream or UDC le to use the VOLUTIL utility instead. :ALTVSET command not supported (use VOLUTIL instead).
D-58 Incompatibilities
2052 MESSAGE MODE CAUSE ACTION 2053 MESSAGE MODE CAUSE ACTION 2054 MESSAGE MODE CAUSE ACTION 2055 MESSAGE MODE CAUSE ACTION :COBOLGO command not supported. CM and NM incompatibility detected by MPT (severity level ERROR). The :COBOLGO command is used to compile, prep, and run a COBOL 68 program at one time. The COBOL 68 compiler is not available on MPE/iX. Remove all references to the :COBOLGO command from the job or UDC le. :COBOLPREP command not supported.
D-60 Incompatibilities
2056 MESSAGE MODE CAUSE ACTION 2057 MESSAGE MODE CAUSE ACTION 2100 MESSAGE MODE CAUSE ACTION 2101 MESSAGE MODE CAUSE ACTION :RUN ASOCTBL# - not supported (use ASOCTBL instead). CM and NM incompatibility detected by MPT (severity level WARNING). The ASOCTBL5 program was used on MPE V/E systems to associate a user with a device class. This function is replaced by the ASOCTBL program on MPE iX. Modify the job or UDC le to use the ASOCTBL program instead of the ASOCTBL5 program.
2102 MESSAGE MODE CAUSE ACTION 2103 MESSAGE MODE CAUSE ACTION 2104 MESSAGE MODE CAUSE ACTION D-62 Incompatibilities User SL has externals not satis ed in system SL. CM and NM incompatibility detected by MPT (severity level POSSIBLE). This SL has external references which are not found in the system SL. This may not be a problem provided the externals are found in an account (PUB) SL. Otherwise, programs using this SL may fail to run.
2105 MESSAGE MODE CAUSE ACTION 2106 MESSAGE MODE CAUSE ACTION 2107 MESSAGE MODE CAUSE ACTION Program calls system UNCALLABLE procedure. CM and NM incompatibility detected by MPT (severity level WARNING). This program makes calls to an UNCALLABLE system procedure. Normally uncallable procedures should be referenced only by MPE, and they require that the program run in Privileged Mode.
2108 MESSAGE MODE CAUSE ACTION 2999 MESSAGE MODE CAUSE ACTION D-64 Incompatibilities Group SL requires PUB SL routines. NM incompatibility detected by MPT (severity level POSSIBLE). A group SL has external references which are not satis ed from the system SL. An SL was found in the PUB group of this account which satis es these references. Ensure that the PUB SL is migrated at the same time as the group SL. Programs which reference routines from this group SL may also require the PUB SL to be present.
E Notes on Migrating VPLUS For the most part, VPLUS operates the same on MPE/iX-based machines as it does on MPE V/E-based machines. This is because all of VPLUS operates in CM. NM stubs are supplied for all of the VPLUS intrinsics so that they may be called from NM applications. The following VPLUS utilities are available in CM: FORMSPEC REFSPEC REFORMAT ENTRY Migration Issues Terminal Configuration Supported Terminals The following headings discuss VPLUS migration issues.
HP 2625A HP 2628A HP 7009X The following terminals are supported if the rmware revision conditions in parentheses are met: HP 2622A (rev D 1818-3199) HP 2623A (rev B 1818-3223) HP 2624B (rev B 1818-3139) HP 2627A (rev B 1818-3487) Unsupported Terminals Pascal Integers E-2 The following terminals are not supported: HP 2382A HP 2621A HP 2621B HP 2621P HP 2626A HP 2626W HP 264x HP 3075 HP 3076 HP 3081A In HP Pascal/iX, all references to integers in the COMAREA must be of type SHORTINT (a new 2-byte compiler
Data Alignment Real Data Types NM Stubs Terminal Refresh Vectra With Type Ahead Enabled VPLUS intrinsics continue to expect data that is aligned on 16-bit boundaries. For example, in a Pascal program, the record structures declared for the VPLUS INFO intrinsics may need to be packed to ensure 16-bit data alignment. Real data type conversions continue to assume Hewlett-Packard real format for VGETREAL, VGETLONG, VPUTREAL, and VPUTLONG.
eld contains YES, change the value to NO. Save the new value by pressing the 4F15 key. If a block mode application is run on a Vectra while the \Type Ahead" value is set to YES, a form will be painted. However, the keyboard will remain in a locked state. To clear this terminal hang, press 4CTRL5 4F105 to ush the type ahead bu er. Next, press the 4F85 key to exit the application. Follow the directions above to recon gure the \Type Ahead" eld on the Terminal Con guration Screen.
Non-VPLUS I/O Often, application designers resort to using FREAD, FWRITE, and input/output verbs of a programming language to display and retrieve information from the terminal within the VPLUS context. The situation becomes more complex when the application also controls the terminal settings as well as the driver settings. A likely end result is an application which runs in a restricted environment, such as on an ATP, and on one kind of terminal only.
VGETIEEEREAL The VGETIEEEREAL intrinsic copies character-coded data from a speci ed eld in the form data bu er in memory into an application, converting the numeric value to IEEE oating-point format. The syntax and parameter descriptions for this intrinsic are provided below. VGETIEEEREAL {COMAREA,FIELDNUM,VARIABLE} COMAREA Must be COMAREA name speci ed when the forms le was opened with VOPENFORMF.
position in the data bu er.) The eld's value must be numeric, but its data type need not be. That is, numbers in a character type eld can be converted. The numeric value, stored in the bu er in character coded form, is converted to IEEE format and then moved to the variable in the application. If errors occur during conversion, CSTATUS is set to an error code. If the requested eld's error ag is set, its value is moved to the variable, but CSTATUS is set to an error code.
VGETIEEELONG The VGETIEEELONG intrinsic copies character-coded data from a speci ed eld in the form data bu er in memory into an application, converting the numeric value to IEEE long oating-point format. The syntax and parameter descriptions for this intrinsic are described below. VGETIEEELONG {COMAREA,FIELDNUM,VARIABLE} COMAREA Must be the COMAREA name speci ed when the forms le was opened with VOPENFORMF.
FORMSPEC and is totally independent of the eld position in the data bu er). The eld's value must be numeric, but its data type need not be. That is, numbers in a character type eld can be converted. The numeric value, stored in the bu er in charactercoded form, is converted to IEEE long format and then moved to the variable in the application. If errors occur during conversion, CSTATUS is set to an error code.
VPUTIEEEREAL The VPUTIEEEREAL intrinsic writes a oating-point number in IEEE standard format from an application to a speci ed eld in the form data bu er in memory, converting the value to character-set-coded external representation. The syntax and parameter descriptions for this intrinsic are provided below. VPUTIEEEREAL {COMAREA,FIELDNUM,VARIABLE} COMAREA Must be the COMAREA name speci ed when the forms le was opened with VOPENFORMF.
external representation and copied to a eld in the data bu er. This procedure converts an IEEE oating-point real number to its character-coded form and writes the converted value to a particular eld in the data bu er, right justi ed. The exact format of the written data depends on the type of the destination eld. For example, if the number \34.56" were to be put in a eld of type DIG, the result would be \34", since a eld of type DIG may only contain integer values.
VPUTIEEEREAL(COMAREA,FIELDNUM,VARIABLE); VPUTIEEELONG Writes a oating point number in IEEE long standard format from an application to a speci ed eld in the form data bu er in memory, converting the value to character-set-coded external representation. The syntax and parameter descriptions for this intrinsic are provided below. VPUTIEEELONG {COMAREA,FIELDNUM,VARIABLE} COMAREA Must be the COMAREA name speci ed when the forms le was opened with VOPENFORMF.
VARIABLE identi ed by FIELD may not be longer than 80 characters. Variable of type IEEE long oating-point real numbers (64-bits) that contains the value to be converted to character-set-coded external representation and copied to a eld in the data bu er. This intrinsics converts an IEEE long oating-point real number to its character-coded form and writes the converted value to a particular eld in the data bu er, right-justi ed.
CALL "VPUTIEEELONG" USING COMAREA FIELDNUM VARIABLE. FORTRAN: CALL VPUTIEEELONG(COMAREA,FIELDNUM,VARIABLE) Pascal: VPUTIEEELONG(COMAREA,FIELDNUM,VARIABLE); VTURNOFF The VTURNOFF intrinsic turns o VPLUS block mode and enables character mode access without disturbing the terminal screen. The syntax and parameter descriptions for this intrinsic are provided below. VTURNOFF {COMAREA} COMAREA Must be COMAREA named when le was opened by VOPENTERM.
VTURNOFF recon gures the terminal and driver for character mode operations without disturbing the screen image on the terminal. The following operations normally performed in VCLOSETERM are not performed in VTURNOFF: Clear local form storage Enable the USER/SYSTEM keys Disable touch reporting, delete touch elds Clear screen Unlock keyboard Close terminal le Note that VTURNOFF does not close the terminal le. To close the le and completely reset the driver and the terminal, VCLOSETERM must be used.
VTURNON The VTURNON intrinsic turns on VPLUS block mode without disturbing the terminal screen. The syntax and parameter descriptions for this intrinsic are provided below. VTURNON {COMAREA,TERMFILE} COMAREA The COMAREA name must be unique for each open forms le. The COMAREA must be the same COMAREA used in VOPENTERM. The following COMAREA items must be set before the call, if not already set: CSTATUS Set to zero. LANGUAGE Set to code that identi es the programming language of the calling program.
TERMFILE Must be the same terminal le name used in VOPENTERM. VTURNON is normally used in an application when the terminal is already opened by VOPENTERM, and VTURNOFF was called to switch out of VPLUS block mode. VTURNON switches the application back to VPLUS block mode without disturbing the image on the terminal screen.
SPL: MOVE T1:=" "; VTURNON(COMAREA,T1); Pascal: T1:=` '; VUTURNON(COMAREA,T1); VBLOCKWRITE The VBLOCKWRITE intrinsic writes a block of characters to a terminal in block mode. The syntax and parameter descriptions for this intrinsic are provided below. VBLOCKWRITE {COMAREA,BUF,LEN,TMODE,LOC,TC} COMAREA The following COMAREA elds must be set before calling VBLOCKWRITE, if not already set: LANGUAGE Set to code identifying the programming language of the calling program.
BUF LEN TMODE LOC Byte array containing characters to be written to the terminal. Number of bytes in the BUF array (2-byte integer). Terminal mode (2-byte integer). 0 do not change terminal mode 1 change to format mode 2 change to unformatted mode Start position of write (array of two 2-byte integers). Absolute cursor addressing is not allowed in format mode. An error will be returned. [0] [0] home cursor before WRITE [x] [y] TC start from absolute row x, column y. (Not allowed in format mode.
1 unlock at the end of write. lock keyboard at the beginning of write; unlock at the end of write. This procedure writes the content of a user bu er to a terminal. TMODE options can be used to change the terminal to format or unformatted mode before the write. LOC options allow the programmer to specify the position of the screen where the write is to begin. Terminal control (TC) options can be used to control keyboard locking for the protection of data as it is being written to the terminal.
COBOL: CALL "VBLOCKWRITE" USING COMAREA @BUF LEN TMODE LOC TC. BASIC: CALL VBLOCKWRITE(C(*),B1$,L1,M1,L(*),T1) FORTRAN: CALL VBLOCKWRITE(COMAREA,BUF,LEN,TMODE,LOC,TC) SPL: VBLOCKWRITE(COMAREA,BUF,LEN,TMODE,LOC,TC); Pascal: VBLOCKWRITE(COMAREA,BUF,LEN,TMODE,LOC,TC); VBLOCKREAD The VBLOCKREAD intrinsic reads a block of characters from a terminal in block mode. The syntax and parameter descriptions for this intrinsic are provided below.
VBLOCKWRITE may set the following COMAREA elds: Set to nonzero value if call is unsuccessful. FILERRNUM Set to le error code if MPE le error. Byte array to receive data from the terminal. Maximum number of bytes to read from terminal (2-byte integer). Actual number of bytes read from terminal (2-byte integer). Terminal setting at the time of read (2-byte integer). 1 assume terminal is in format mode 2 assume terminal is in unformatted mode Array of two 2-byte integers containing start position of read.
application bu er. There is no VPLUS form associated with the read. Like the companion intrinsic, VBLOCKWRITE, this procedure is recommended only for advanced programmers who are pro cient with terminal input/output. VOPENTERM must be called before using VBLOCKREAD. The keyboard must be unlocked before calling VBLOCKREAD. (Refer to keyboard unlock options in VBLOCKWRITE.) VBLOCKREAD will lock the keyboard immediately after 4Enter5 or a function key is pressed to ensure data integrity.
BASIC: CALL VBLOCKREAD(C(*),B1$,L1,L2,M1,L(*),U1,U2) FORTRAN: CALL VBLOCKREAD(COMAREA,BUF,LEN,ACTLEN,TMODE,LOC,BC,TC) SPL: VBLOCKREAD(COMAREA,BUF,LEN,ACTLEN,TMODE,LOC,BC,TC); Pascal: VBLOCKREAD(COMAREA,BUF,LEN,ACTLEN,TMODE,LOC,BC,TC); E-24 Notes on Migrating VPLUS
F Using the GETUDC Utility This appendix describes how to use the GETUDC utility. GETUDC is intended to be used during the preparation stage of the migration e ort. GETUDC runs on MPE V/E-based systems (release G.03.01 and later). Included in this appendix are discussions on the following subjects: \GETUDC Operation", a general overview on when to use the tool and how the tool operates. \Using GETUDC", a detailed description of the user interface.
The name COMMAND.PUB.SYS, a system le that keeps track of the names of all system-recognized UDC les, as well as the users associated with those UDC les. The names of all system-recognized UDC les located on your MPE V/E-based computer system. Note A system-recognized UDC le is one that a user has speci ed with the :SETCATALOG command as being either a system-level, account-level, or user-level UDC le. You should use GETUDC immediately before creating the SYSDUMP tape you are planning to use with DIRMIG.
Using GETUDC Initiate GETUDC by running the program le GETUDC.PUB.SYS either interactively or in batch mode. GETUDC progresses through the following steps in order to accomplish its task: 1. Asks you for an MPE le name, then creates and opens an EDIT/V compatible text le you can later use as an indirect STORE le. 2. After writing the name COMMAND.PUB.SYS to the indirect STORE le, GETUDC reads system-recognized UDC le names from a temporary copy of COMMAND.PUB.
A question mark (?) displays pertinent HELP text, then returns you to the prompt. A 4Return5 terminates GETUDC (a le is not created). If you specify an illegal le name, or if a duplicate le name already exists on the system, GETUDC displays an error message and prompts you again for a le name. Once a le name is selected, GETUDC creates an EDIT/V-compatible text le you can later use as an indirect STORE le at the appropriate SYSDUMP prompt.
A lockword, if previously speci ed, is not displayed in the above message. Appending Other File Sets Note You can append additional le names to the indirect STORE le. When the indirect STORE le name is used as a response to the ENTER DUMP FILE SUBSETS prompt of the SYSDUMP, these les will be stored in the STORE portion on the SYSDUMP tape immediately following COMMAND.PUB.SYS and UDC les.
GETUDC displays this prompt: Enter any file sets you want to append [ enter ? for help ] >> The possible responses to this prompt are: Any STORE/RESTORE-compatible le set name. Please enter this data correctly, as GETUDC does not check for incorrect names. You are prompted repeatedly until you press 4Return5 without entering a le set name. A question mark (?) displays pertinent HELP text, then returns you to the prompt. A 4Return5causes GETUDC to save and close the indirect STORE le, terminate.
>> @M >> A@#ACCT@ >> @.@.FINANCE >> 4Return5 END OF PROGRAM : Example F-1. GETUDC Execution Example GETUDC Program Error Messages GETUDC sets the user-de ned Job Control Word (JCW) GUERR to a value that indicates the error or warning that occurred. If no error or warning occurred, GUERR is set to zero. When running interactively, some errors do not cause GETUDC to terminate. When running in batch mode, if any error is encountered, GETUDC terminates with an appropriate error message.
0000 to 1000 1001 MESSAGE The GUERR value is equivalent to a le system error number. The returned message is a le system error message. CAUSE ACTION A le system error has occurred. Look up the indicated le system error in the MPE V/E Intrinsics Reference Manual (32033#90007) and take appropriate action. MESSAGE CATOPEN INTRINSIC ERROR:error number FILE: GUCATnnn .PUB.SYS UNABLE to OPEN THE MESSAGE CATALOG FILE (GUERR 1001) ACTION GETUDC is unable to open the NLS language catalog le.
1005 1006 MESSAGE le system error message (FSERR nnn ) FILE: COMMAND.PUB.SYS UNABLE TO OPEN THE FILE COMMAND.PUB.SYS. (GUERR 1005) CAUSE ACTION GETUDC needs the le COMMAND.PUB.SYS in order to gather all UDC les from the system. It is unable to open the le, because the le is not present or because of other le system errors. Look up the indicated le system error and take appropriate action. MESSAGE ATTEMPT TO WRITE BEYOND END OF FILE.
1010 MESSAGE le system error message (FSERR nnn ) FILE: DUPCOMMD .group.account UNABLE TO OPEN TEMPORARY COPY OF COMMAND.PUB.SYS. (GUERR 1010) CAUSE ACTION 1011 MESSAGE CAUSE ACTION 1012 MESSAGE GETUDC copies the le COMMAND.PUB.SYS to a temporary le and scans this temporary le instead. It is unable to open this le. Look up the le system error, refer to the MPE V/E Intrinsics Reference Manual (32033-90007), and take appropriate action. le system error message (FSERR nnn ) FILE: DUPCOMMD .group.
1014 1015 2001 MESSAGE INCORRECT FILE FORMAT FOR COMMAND.PUB.SYS. (GUERR 1014) CAUSE ACTION The le COMMAND.PUB.SYS is in an incorrect le format (record size is less than 20 words and/or the le is an ASCII le). Purge the le COMMAND.PUB.SYS, rebuild the le in correct format, and perform :SETCATALOG commands appropriately to recreate the UDC environment in the system. MESSAGE COMMAND.PUB.SYS IS CORRUPTED. CAUSE ACTION The le COMMAND.PUB.SYS is corrupted.
2004 2005 MESSAGE COMMAND.PUB.SYS IS EMPTY. (GUWARN 2004) CAUSE ACTION The le COMMAND.PUB.SYS is empty. No action required. MESSAGE ERROR RETURNED FROM FCHECK INTRINSIC. CAUSE Unknown. No action required. ACTION 2006 MESSAGE (GUWARN 2005) le system error message (FSERR nnn ) FILE: DUPCOMMD .group.account UNABLE TO CLOSE TEMPORARY COPY OF COMMAND.PUB.SYS. (GUWARN 2006) CAUSE ACTION F-12 GETUDC is unable to close the temporary copy of COMMAND.PUB.SYS after the scan is completed.
G Using the Directory Migration Tool DIRMIG is intended to be used during the installation stage of the migration process, after the MPE/iX operating system has been installed and con gured on a 900 Series HP 3000 computer system. DIRMIG runs on MPE iX-based systems. Included in this appendix are discussions on the following subjects: \DIRMIG Operation", a general overview of the tool and how it operates. \Using DIRMIG", a detailed description of the user interface.
DIRMIG Operation DIRMIG is an MPE/iX tool you use to migrate an MPE V/E operating environment (U-MIT or later) to an MPE/iX-based computer system. DIRMIG provides a friendly, menu-driven interface that enables you to easily migrate operating environment information located on the MPE V/E SYSDUMP tape created during the preparation stage of the migration process. Refer to the discussion of creating the SYSDUMP tape in Chapter 3, \Preparation".
DIRMIG creates a log le each time it executes. DIRMIG log les contain migration progress messages as well as error messages about components that could not be migrated successfully. The log le provides information for debugging and troubleshooting if a problem occurs during migration. The DIRMIG log les are numbered so that you can maintain a log le history of every execution of DIRMIG.
There is no access to MPE/iX commands. Caution G-4 You should not interrupt or abnormally terminate DIRMIG once it is started, since it is running in Privileged Mode (PM) updating MPE/iX system tables and allocating directory space. Instead, use the exit options provided to exit DIRMIG safely.
Using the Directory Migration Tool Figure G-1.
If DIRMIG is executed interactively, it is recommended that the system be in \single-user mode". Single-user mode is achieved by executing the LOGOFF command at the system console: A =LOGOFF #Snnn 4CTRL5 where #Snnn is the session number assigned to MANAGER.SYS which remains logged on. Single-user mode guarantees that only one user is on the system, and that no one else can log on until you disable single-user mode after DIRMIG nishes execution.
:FILE MYTAPE;DEV=MAGTAPE :FILE MYTAPE=*MYTAPE 4. If device class LP is not con gured for your system, create a le equation to redirect LIST (DIRMIG's formal designator for the o ine listing device) to the device class or logical device number for your line printer or an alternate device (refer to \Redirecting DIRMIG Output"). 5. Enter :RUN DIRMIG.PUB.SYS. DIRMIG displays the Main Menu where you can select your migration options.
Under subsequent headings you will nd discussions on how to use DIRMIG's menu-driven interface to select, then implement, the MPE V/E operating environment migration options of your choice: 1. Selecting Your Migration Options from the Main Menu 2. Migrating Without Dialog 3. Migrating With Dialog 4. Migrating Global RINs 5. Migrating User-Logging Identi ers 6. Migrating the Directory 7. Migrating Private Volume Environments 8.
d c a ============================================================ DIRMIG.PUB.SYS HP30362A.00.00 (c) HEWLETT PACKARD CO., 1987. MPE/iX Migration Utility. WED, SEP 23, 1987, 4:55 PM ============================================================ Current Log File: DIRLOGO3.PUB.SYS CHOOSE FROM MIGRATION OPTIONS BELOW: 0 - EXIT 1 - HELP 2 - COMPLETE MIGRATION (No Dialog) 3 - COMPLETE MIGRATION (With Dialog) 4 - RINS 5 - USER LOGGING ID'S 6 - DIRECTORY 7 - PRIVATE VOLUME ENVIRONMENT ENTER MIGRATION OPTION (S) ..
You are being asked which migration paths you want to take. At the ENTER MIGRATION OPTION(S) prompt, you can select options 0, 1, 2, and 3 by themselves or select one or more of options 4, 5, 6, and 7 in the following formats: Option numbers separated by commas. The example below indicates you selected options 4, 6, and 7: ENTER MIGRATION OPTION(S) ..4, 6, 7 Option number separated by a \/" to show a range of selections.
If you select option 3 from the Main Menu, DIRMIG enables you to step through each of the optional menus in turn so that you can implement your own migration strategy. Refer to \Migrating with Dialog". If you select option 4 from the Main Menu, you proceed directly to the Global RIN Migration Menu. Refer to \Migrating Global RINs". If you select option 5 from the Main Menu, you proceed directly to the User-Logging ID Migration Menu. Refer to \Migrating User-Logging Identi ers".
If you select option 6 from the Main Menu, you proceed directly to the Directory Migration Menu. Refer to \Migrating the Directory". If you choose to migrate one or more accounts, the UDC Environment/User Files Migration Menu is displayed. Refer to \Migrating UDC Environments and User Files". If you select option 7 from the Main Menu, you proceed directly to the Private Volume Migration Menu. Refer to \Migrating Private Volume Environments".
all volume sets found. (Refer to \Migrating Private Volume Environments" for details about PVASSIST and PVSUMARY les.
Migrating With Dialog Migrating Global RINs If you select option 3 from the Main Menu, DIRMIG enables you to step through each of the following menus in turn so that you can choose your own migration path. Once you are nished with each optional menu, DIRMIG moves you to the next menu on the path: 1. Global RIN Migration Menu (refer to \Migrating Global RINs"). 2. User-Logging ID Migration Menu (refer to \Migrating User-Logging Identi ers"). 3. Directory Migration Menu (refer to \Migrating the Directory").
d 0 1 2 3 4 c a RIN MIGRATION ------------CHOOSE FROM RIN OPTIONS BELOW: - EXIT / (No RIN Migration) HELP LIST GLOBAL RINS DELETE GLOBAL RINS MIGRATE RINs ENTER RIN OPTION >> b Figure G-3.
DIRMIG prompts you to select one of the above options. Entering only a 4Return5 at the ENTER RIN OPTION prompt returns you to the same prompt. The following headings explain the di erent options available to you through the RIN Migration Menu. Exit/No RIN Migration (Option 0) If you select option 0 from the RIN Migration Menu, DIRMIG does not migrate RINs.
If you are running DIRMIG interactively, DIRMIG enables you to redirect output to an o ine listing by prompting you with the following message: OFFLINE LISTING (YES/[NO])? >> If you enter Y or YES at the prompt, DIRMIG redirects output to the device associated with the le LIST. The default device speci cation for LIST is LP, but a le equation can be created prior to running DIRMIG that redirects output to an alternate device (refer to \Redirecting DIRMIG Output").
Delete Global RINs (Option 3) If you select option 3 from the RIN Migration Menu, DIRMIG allows you to select the global RINs you do not want migrated to MPE/iX. DIRMIG issues the prompt: ENTER RIN NUMBER(S)>> At this prompt, you can use one of the following formats to specify the RINs you do not want migrated: One RIN per line.
from the SYSDUMP tape (minus any RINs you may have deleted). Once migration is successful, DIRMIG displays the message: RIN MIGRATION SUCCESSFUL Note DIRMIG overwrites all global RIN data existing on the MPE/iX system with the MPE V/E global RIN data you migrated using DIRMIG's RIN Migration Menu.
DIRMIG's next action is dependent upon which option you previously selected in the Main Menu: If you selected option 3 from the Main Menu, DIRMIG takes you to the next menu in the migration path, the User-Logging ID Migration Menu (refer to \Migrating User-Logging Identi ers"). If you selected only option 4 from the Main Menu, DIRMIG terminates.
d 0 1 2 3 c a USER-LOGGING ID MIGRATION ------------------------CHOOSE FROM USER-LOGGING OPTIONS BELOW: - EXIT/ (No Logging ID Migration) HELP LIST USER-LOGGING IDs MIGRATE USER-LOGGING IDs ENTER USER-LOGGING OPTION >> b Figure G-4. User-Logging ID Menu DIRMIG prompts you to select one of the above options. If you enter only 4Return5 at the ENTER USER-LOGGING OPTION prompt, DIRMIG returns you to the same prompt.
Exit/No Logging ID Migration (Option 0) If you select option 0 from the User-Logging ID Migration Menu, DIRMIG does not migrate user-logging identi ers. DIRMIG's next action is dependent upon which option you previously selected in the Main Menu: If you selected option 3 from the Main Menu, DIRMIG takes you to the next menu in the migration path, the Directory Migration Menu (refer to \Migrating the Directory"). If you selected only option 5 from the Main Menu, DIRMIG terminates.
LIST. The default device speci cation for LIST is LP, but a le equation can be created prior to running DIRMIG that redirects output to an alternate device (refer to \Redirecting DIRMIG Output"). If you enter N, NO, or [Return], or if DIRMIG is running in batch mode, output is directed to $STDLIST.
Migrate User-Logging IDs (Option 3) If you select option 3 from the User-Logging ID Migration Menu, DIRMIG migrates to MPE/iX all user-logging identi ers found on the MPE V/E SYSDUMP tape. Once migration is successful, DIRMIG displays the message: USER-LOGGING ID MIGRATION SUCCESSFUL Note DIRMIG overwrites all user-logging identi er information existing on the MPE/iX system with the user-logging identi er information from the MPE V/E SYSDUMP tape.
d 0 1 2 3 4 c a DIRECTORY MIGRATION ------------------CHOOSE FROM DIRECTORY OPTIONS BELOW: - EXIT/(No Directory Migration) HELP LIST ACCOUNTS COMPLETE MIGRATION (All Accounts) PARTIAL MIGRATION (Specified Accounts) ENTER DIRECTORY OPTION >> b Figure G-5.
DIRMIG prompts you to select one of the above options. If you enter only 4Return5 at the ENTER DIRECTORY OPTION prompt, DIRMIG returns you to the same prompt. The following headings explain the di erent options available to you through the Directory Migration Menu. Exit/No Directory Migration (Option 0) If you select option 0 from the Directory Migration Menu, DIRMIG does not migrate MPE V/E directory structures.
If you are running DIRMIG interactively, DIRMIG enables you to redirect output to an o ine listing by prompting you with: OFFLINE LISTING (YES/[NO])? >> If you enter Y or YES at the prompt, DIRMIG redirects output to the device associated with the le LIST. The default device speci cation for LIST is LP, but a le equation can be created prior to running DIRMIG that redirects output to an alternate device (refer to \Redirecting DIRMIG Output").
Migration of Accounts (Options 3, 4) If you select option 3 (Complete Migration of All Accounts) or Option 4 (Partial Migration of Speci ed Accounts) from the Directory Migration Menu, DIRMIG follows a two-step process for account migration: 1. Selects the accounts to migrate. 2. Migrates the accounts. The only di erence between option 3 and option 4 of the Directory Migration Menu concerns how DIRMIG selects accounts to migrate. The di erences between option 3 and option 4 are discussed below.
MPE wild cards are allowed; for example, M@ speci es all accounts beginning with the letter \M". Minus subsets are allowed; for example A@ACCT@ speci es all accounts beginning with the letter \A" except those accounts beginning with the four-letter string \ACCT". Accountsets must be separated by commas. You can enter as many accountsets as desired up to a maximum of 280 characters.
After DIRMIG has selected the directory structure to be migrated (but before directory migration proceeds), DIRMIG allows you to specify whether or not you want DIRMIG to overwrite current MPE/iX directory information with MPE V/E directory information whenever account/group names con ict. DIRMIG displays this prompt: Completing Account Migration.
DIAG.
d DIRMIG migrates each account, followed by the groups within the account. When a group associated with a private volume has been migrated, that group's volume set information is saved to PVASSIST.PUB.SYS. After the account's groups are migrated, the account's users are migrated.
If you supply an MPE/iX supported password (eight or less alphanumeric characters, beginning with an alphabetical character) at this prompt, DIRMIG replaces all encrypted passwords it encounters on the SYSDUMP tape with the password you speci ed. If you enter blanks or 4Return5, DIRMIG replaces each encrypted password with the name of the object being migrated. For example, if account XTRA contains an encrypted password, then XTRA is the replacement password for the XTRA account.
DIRMIG's next action is dependent upon the following considerations: If you selected option 3 from the Main Menu and volume set de nitions were appended to the le PVASSIST.PUB.SYS when you migrated one or more accounts to MPE/iX , DIRMIG takes you to the next menu in the migration path, the Private Volume Migration Menu (refer to \Migrating Private Volume Environments").
MPE/iX volume media with MPE V/E directory information. Note Read Overview of \Private Volume Migration" before using DIRMIG's Private Volume Migration Menu to generate VOLUTIL command les. For more information concerning VOLUTIL and volume management on MPE/iX, refer to the Volume Management Reference Manual (32650-90045).
Overview of Private Volume Migration The Private Volume Migration Menu serves the purpose of generating command les you can use later with VOLUTIL, the MPE iX volume management utility. These command les enable you to recreate an MPE V/E private volume environment on your MPE/iX system. Private volume migration is a two-step process: 1. Using DIRMIG's Private Volume Migration Menu to generate VOLUTIL command les. 2. Using VOLUTIL to initialize MPE/iX volume media with MPE V/E directory information.
You can restore the les associated with a private volume after you have successfully recreated that private volume's directory structure on MPE/iX. The Private Volume Migration Menu provides options to build two types of command les. The rst type of le is a general command le that will migrate the entire MPE V/E private volume environment to MPE/iX. The name of this le is PVSUMARY.PUB.SYS. Before it can be used by VOLUTIL, however, you must customize it by providing speci c logical device numbers.
Volume set command les contain a subset of information from PVSUMARY.PUB.SYS; speci cally the commands to migrate one volume set to MPE/iX. Volume set command les may be used with VOLUTIL as soon as they are created, while PVSUMARY.PUB.SYS must be customized rst. Once created, either le type can be customized (edited) and/or used at any time.
drives equal the number of members plus the master. Understanding this concept will facilitate both volume set command le generation and the customization of PVSUMARY.PUB.SYS. Command le customization is detailed in Using VOLUTIL to \Complete Private Volume Migration". Selecting Your Menu Option From the Private Volume Migration Menu shown in Figure G-7, you can choose the Private Volume migration option you wish.
Exit/No Volume Set Migration (Option 0) If you select option 0 from the Private Volume Migration Menu, DIRMIG does not generate VOLUTIL command les. DIRMIG's next action is dependent upon which option you previously selected in the Main Menu: If you selected option 3 from the Main Menu and you successfully migrated one or more accounts using DIRMIG's Directory Migration Menu, DIRMIG takes you to the UDC Environment/User Files Migration Menu (refer to \Migrating the UDC Environment and User Files").
but a le equation can be created prior to running DIRMIG that redirects output to an alternate device (refer to \Redirecting DIRMIG Output"). If you enter N, NO or 4Return5 or if DIRMIG is running in batch mode, output is directed to $STDLIST.
prompt (without specifying any accountsets) DIRMIG returns you to the ENTER PRIVATE VOLUME OPTION prompt of the Private Volume Migration Menu.
Accountsets are de ned to be one or more MPE V/E account names, where: MPE wild cards are allowed; for example, M@ speci es all accounts beginning with the letter \M". Minus subsets are allowed for example, A@-ACCT@ speci es all accounts beginning with the letter \A" except for those accounts beginning with the four-letter string \ACCT". Accountsets must be separated by commas. You can enter as many accountsets as desired up to a maximum of 280 characters.
d CHOOSE VOLUME SET OPTION BELOW: 0 1 2 3 4 5 - EXIT (No Volume Set Migration) HELP LIST VOLUME SET DEFINITION GENERATE A COMMAND FILE DELETE VOLUME SET DEFINITION NEXT VOLUME SET DEFINITION ENTER VOLUME SET OPTION >> c Figure G-8.
DIRMIG prompts you to select one of the above options. Entering only 4Return5 at the ENTER VOLUME SET OPTION prompt returns you to the same prompt. The following headings explain the di erent options available to you through the Volume Set Options Menu. If you select option 0 from the Volume Set Options Menu, DIRMIG does not generate a VOLUTIL command le for the selected volume set de nition. Instead, DIRMIG returns you to the ENTER PRIVATE VOLUME OPTION prompt of the Private Volume Migration Menu.
>> DIRMIG creates a command le for the currently selected volume set de nition.
The following rules apply for these prompts: The logical device number of zero for the master volume is not allowed. A command le will not be built if a zero is input for the master volume logical device number. A logical device number of zero or 4Return5 for member volumes. DIRMIG generates commands which will result in the logical initialization of those volumes when the command le is used with VOLUTIL. A logical device number of 1 . . . 255 for member volumes when the command le is used with VOLUTIL.
If you select option 4 from the Volume Set Options Menu, DIRMIG deletes from PVASSIST.PUB.SYS the currently selected volume set de nition. Specify this option when you do not want to migrate the current volume set de nition. Delete Volume Set Definition (Option 4). If you select option 5 from the Volume Set Options Menu, DIRMIG displays the next volume set in the pool of available migratable volume sets (as bounded by the accounts you selected).
DIRMIG displays a Volume Set Options Menu for each volume set de nition located, allowing you to choose your own migration option for each volume set de nition. When no more volume set de nitions are found in PVASSIST.PUB.SYS, DIRMIG returns you to the ENTER PRIVATE VOLUME OPTION prompt of the Private Volume Migration Menu. Generate PVSUMARY Command File (Option 4) If you select option 4 from the Private Volume Migration Menu, DIRMIG generates the command le PVSUMARY.PUB.
You can enter as many accountsets as desired up to a maximum of 280 characters.
You are repeatedly prompted for accountsets until you enter only 4Return5 at the ENTER ACCOUNT SUBSETS prompt. Once DIRMIG completes account selection, DIRMIG proceeds to generate PVSUMARY.PUB.SYS. If PVSUMARY.PUB.SYS already exists, you are prompted for a new command le name. DIRMIG displays the following progress messages: PVSUMARY FILE CREATION IN PROGRESS... PVSUMARY FILE COMPLETED. Note The VOLUTIL command le PVSUMARY.PUB.
Migrating the UDC Environment and User Files DIRMIG displays the UDC Environment/User Files Migration menu shown in Example G-7 only after one of the following actions has occurred: You selected option 3 from the Main Menu and you have successfully migrated one or more accounts from the Directory Migration Menu. You selected option 6 from the Main Menu and you have successfully migrated one or more accounts from the Directory Migration Menu.
the di erent options available to you through the UDC Environment/User Files Migration Menu. Note Options 2,3, and 4 of the UDC Environment/User Files Migration Menu follow the same sequence of ve steps to accomplish UDC environment migration. The only di erence between these three options lies in the choices DIRMIG gives you concerning restoration of user les associated with the accounts you migrated from the MPE V/E SYSDUMP tape (using DIRMIG's Directory Migration Menu).
Migrate UDC Environment/Restore User Files (Options 2, 3, 4) If you select option 2, 3, or 4 from the UDC Environment/User Files Migration Menu, DIRMIG proceeds to migrate the UDC environments associated with the account structures you successfully migrated during directory migration (refer to \Migrating the Directory Structure"). Note DIRMIG invokes the RESTORE facility twice during UDC migration.
If you enter N, NO, or 4Return5, or if DIRMIG is running in batch mode, output is directed to $STDLIST.
UDC migration is divided into ve steps, described below. 1. Obtain MPE/iX UDC environment information. If COMMAND.PUB.SYS exists on the MPE/iX system, DIRMIG performs these actions on COMMAND.PUB.SYS to obtain MPE/iX UDC information and to preserve the current MPE/iX UDC environment: Copies UDC information from COMMAND.PUB.SYS to a temporary data structure. Renames COMMAND.PUB.SYS to SAVECMD.PUB.SYS. DIRMIG later modi es SAVECMD.PUB.SYS when migrating the MPE V/E UDC environment to MPE/iX.
After the MPE V/E system le COMMAND.PUB.SYS is successfully restored on the MPE/iX system, DIRMIG collects the names of the UDC les for those accounts and users successfully migrated. These are the UDC les that are restored during Step 3 (see below). Once these names are collected, DIRMIG purges the COMMAND.PUB.SYS le restored from the SYSDUMP tape and renames the MPE/iX le SAVECMD.PUB.SYS (see Step 1) back to COMMAND.PUB.SYS.
3. Restore UDC les/user les from the SYSDUMP tape. Step 3 varies depending upon whether you selected option 2, option 3, or option 4 from the UDC Environment/User Files Migration Menu. In all three cases, DIRMIG restores those UDC les whose names were collected in Step 2. DIRMIG restores les by invoking the :RESTORE facility with the KEEP and OLDDATE options enabled. (Refer to the :RESTORE command in the MPE/iX Commands Reference Manual (32650-90003) for details.
At this prompt you can enter le subsets you want to migrate. File subsets are de ned to be one or more MPE V/E le names (valid to the MPE/iX :RESTORE command), where le subsets are separated by commas, and MPE wild cards are allowed; for example, M@#.@.@ speci es all les beginning with the letter \M" and ending with a numeric character. You are repeatedly prompted for lesets until you enter only 4Return5 at the ENTER FILE SUBSETS prompt.
Migrate UDC Environment/Restore all Files (Option 4). DIRMIG proceeds to restore from the MPE V/E SYSDUMP tape the UDC les whose names were collected in Step 2, as well as all user les associated with the accounts migrated during directory migration (except those les in PUB.SYS).
Exiting DIRMIG Caution Each menu in DIRMIG has an optional selection that allows you to exit DIRMIG normally. You should not interrupt or abnormally terminate DIRMIG once it is started, since it is running in Privilege Mode updating MPE/iX system tables and allocating directory space. Use exit options provided to exit DIRMIG safely.
Redirecting DIRMIG Output When you select the o ine option available through several DIRMIG menus, you direct the text output to the DIRMIG list le LIST. By default this le is assigned to the system line printer (DEV=LP). If you want to redirect the output to a di erent device, you must, prior to running DIRMIG, create an MPE le equation to rede ne the characteristics for LIST. This le equation is invoked only when you respond Y or YES to an OFFLINE LISTING (YES)/[NO]) prompt.
If you enter N, NO, to the prompt, DIRMIG terminates. You can purge or rename DIRMIG log les (highest to lowest), then rerun DIRMIG. DIRLOGnn contains: Progress messages displayed to $STDLIST. Progress messages for directory migration. Error messages indicating a component has not been migrated.
Verifying Directory Migration Using VOLUTIL to Complete Private Volume Migration To verify that the correct data has been migrated check the system components, listed in the rst column, by using the commands listed in the second column.
Note Customizing PVSUMARY.PUB.SYS For more information concerning the VOLUTIL utility and volume management on MPE/iX, refer to Volume Management (32650-90045). The command le PVSUMARY.PUB.SYS contains VOLUTIL commands to generate the MPE V/E private volume environment on MPE/iX. However, alphanumeric tokens are used in lieu of logical device numbers for VOLUTIL command parameters. You are responsible for editing PVSUMARY.PUB.
d c . . . SCRATCHVOL XX1 NEWSET volume set name VSET1 XX1 SETDEFAULTSET volume set name . . . SCRATCHVOL XX2 NEWVOL XX2 . . . SCRATCHVOL XXn NEWVOL XXn . . . Using an EDIT/V compatible editor, edit PVSUMARY keeping the following rules in mind: You must replace token XX1 with the logical device number of the disk drive upon which the master volume is to be mounted. This value can not be zero.
volume can be associated with the same logical device number. Tokens XX2 through XXn can be zero only if the those volumes will be logically initialized on the master volume. You can physically initialize these volumes with VOLUTIL's command, :INITVOL, at a later time. Any VOLUTIL command or MPE/iX command can be modi ed, added, or deleted at your discretion. However, this is only recommended for those users who are intimately knowledgeable with VOLUTIL and MPE/iX's mountable volumes.
The preceding comments identify which place holders should be replaced by logical device numbers within a particular volume set. Once you make these replacements, PVSUMARY.PUB.SYS is ready for use by VOLUTIL. Performing the Migration Once the VOLUTIL command les are ready (customized), the MPE V/E private volume environment can be migrated.
Command Interpreter read timeout value to at least 15. Reboot the system. A value of 0 indicates that there is no read timeout in e ect and no HPTIMEOUT changes are necessary. The 15-minute timeout is the approximate time to place HP 7933/35 disk drives online and o ine. The command les built by DIRMIG use the 15-minute timer to wait for the Operator to place the volumes online and o ine. 2. Identify those disk packs that will be used for the migration. The volumes should be new or unused.
3. Mount the available volume media into the disk drives. Messages of the following type are posted to the Console: LONER VOLUME MOUNTED ON LDEV 4. (AVR 11) or, UNKNOWN VOLUME MOUNTED ON LDEV 14. (AVR 9) Note Do not proceed to the next step until the system posts AVR messages to the Console for each volume media mounted. 4. Enter the command :DSTAT ALL The status for each of the newly mounted volumes should be one of the following: UNKNOWN, SCRATCH, or LONER.
Enter the command :RUN VOLUTIL.PUB.SYS VOLUTIL drives the private volume migration. The VOLUTIL utility is command driven and provides a HELP facility. You may enter commands by hand to con gure volume sets, however, the command les built by DIRMIG may be input to VOLUTIL to migrate speci c volume set environments. Note Some of the actions described below are timed by the CI variable HPTIMEOUT to allow dismounting and mounting of volume media. Follow each directive in a timely fashion.
Below is the procedure for using the command les. Read all the :COMMENT messages posted to the Console. The input is entered in response to VOLUTIL prompts: 1. USE cmd le Enter the name of the VOLUTIL script le, cmd le , via the VOLUTIL USE command. cmd le may either be the user-modi ed copy of PVSUMARY.PUB.SYS, or one of the individual command les for a speci c volume set. 2.
Continue responding and mounting/dismounting separate disk packs into the speci ed disk drives as directed by VOLUTIL. After the volume set information is migrated to the new volumes, accounts and groups will be built on the volume set.
Verify the Migration Several commands are used to verify the proper migration: Run the VOLUTIL utility by entering the command :RUN VOLUTIL.PUB.SYS. Use the VOLUTIL command, :SHOWSET. The output should indicate the results of the most currently migrated volume set. Use the MPE/iX :LISTACCT command with the ONVS keyword to verify the span of acctname to vsetname .
d a A =LOGOFF #S1222 :RUN DIRMIG.PUB.SYS 4CTRL5 ============================================================ DIRMIG.PUB.SYS HP30362A.00.00 (c) HEWLETT PACKARD CO.,1986. MPE/iX Migration Utility. MON, MAR 23, 1987, 4:44 PM ============================================================ Current Log File: DIRLOG01.PUB.SYS.
d a ENTER ACCOUNT SUBSETS >> PVACCT1 ========= BEGINNING PRIVATE VOLUME MIGRATION =============== VOLUME SET MIGRATION FOR VSET1.PVGROUP1.PVACCT1.
d a CHOOSE VOLUME SET OPTION BELOW: 0 - EXIT/(No Volume Set Migration) 1 - HELP 2 - LIST VOLUME SET DEFINITION 3 - GENERATE A COMMAND FILE 4 - DELETE VOLUME SET DEFINITION 5 - NEXT VOLUME SET DEFINITION ENTER VOLUME SET OPTION >> 0 NO MORE VOLUME SETS TO PROCESS.
The migration is performed on the System Console. The mount and dismount messages are shown. The following routine uses the command le VSET1CMD created in the previous routine. (PVSUMARY could also have been used.) Note these points in the following routine: The user must issue a :VSCLOSE on VSET2.GROUP1.ACCOUNT on ldev 3 before continuing with VOLUTIL. The error issued by :SCRATCHVOL on ldev 14 for the UNKNOWN volume does not a ect the subsequent :NEWVOL command.
d a :SHOWVAR HPTIMEOUT HPTIMEOUT = 0 :SETVAR HPTIMEOUT 15 : VSET2.GROUP1.ACCOUNT VOLUME MOUNTED ON LDEV 3 (AVR 7) UNKNOWN VOLUME MOUNTED ON LDEV 14 (AVR 9) :DSTAT ALL LDEV-TYPE ----------1-079350 2-079350 3-079350 14-079350 STATUS --------MASTER MEMBER MASTER UNKNOWN VOLUME (VOLUME SET - GEN) --------------------------MEMBER1 (MPEiX_SYSTEM_VOLUME_SET) MEMBER2 (MPEiX_SYSTEM_VOLUME_SET) VSET2 (VSET2.GROUP1.ACCOUNT) :VSCLOSE VSET2.GROUP1.ACCOUNT :RUN VOLUTIL.PUB.SYS Volume Utility 8.30.
d a UNRECOGNIZABLE MPE/iX DISC VOLUME CONTINUE WITH DISC INITIALIZATION ON LDEV 14 (Y/N)? Y volutil: volutil: volutil: volutil: volutil: volutil: volutil: volutil: volutil: volutil: volutil: volutil: volutil: :COMMENT :COMMENT ------------------------------------------------------------:COMMENT The following sequence of commands enables the user :COMMENT to dismount a volume set member in order to initialize :COMMENT a new member on the same ldev.
d a ENTER WHEN VOLUME IS ON-LINE: DISMOUNT REQUEST FOR LDEV 14 GRANTED (AVR 12) LONER VOLUME MOUNTED ON LDEV 14 (AVR 11) 4Return5 volutil: :VSOPEN VSET1.PVGROUP1.PVACCT1 VSET1.PVGROUP1.
Private Volume Migration Checklist Below is a checklist of the major steps of private volume migration. Migrate private volume accounts to MPE/iX with DIRMIG.PUB.SYS. Create PVSUMARY.PUB.SYS and/or volume set command les with DIRMIG. Customize PVSUMARY.PUB.SYS. Identify all necessary volume media. Ensure that HPTIMEOUT is con gured to at least 15 minutes. Verify the VOLUTIL command les for correctness. Run VOLUTIL.PUB.SYS and use the appropriate command les. Label the disk packs as they are generated.
which caused the error, as well as a description of recommended actions to take for error recovery. Operating System Errors Operating system errors generated by the directory service routines will be posted to DIRLOGnn . DIRMIG will attempt to provide conclusive error messages if these errors occur. If errors occur, the following rules apply: 1. If an error occurs during the creation or altering of an account, the users and groups will not be migrated.
and MPE V/E commands are useful for creating objects not successfully migrated by DIRMIG: MPE V/E, MPE/iX MPE XL ONLY MPE V/E ONLY :NEWACCT :VOLUTIL :SYSDUMP :ALTACCT :SYSGEN :RELOAD :NEWGROUP :INSTALL :ALTGROUP :NEWUSER :ALTUSER :PURGEACCT :PURGEGROUP :PURGEUSER :LISTACCT :LISTGROUP :LISTUSER :FREERIN :GETRIN :RELLOG :GETLOG :SETCATALOG If RESTORE of the MPE V/E COMMAND.PUB.SYS fails, the original MPE/iX UDC environment, if one existed, will remain intact on the system.
If RESTORE of UDC les or user les fails, study the SYSLIST for errors. The original MPE/iX UDC environment will remain intact. If UDC environment modi cations were successful, the UDC les may be restored when DIRMIG completes execution. If there are disk space errors, adjustments to the disk space can be made when DIRMIG terminates. The user can :SETCATALOG as necessary to complete the UDC migration process. If UDC modi cation not successful, examine the current DIRLOGnn .PUB.
7001 to 7999 Note G-86 UDC Migration Errors Error messages 5020, 5021, and 5022 are multi-line directory migration errors that provide special detail. They are described in the following section \Directory Corruption Error Messages".
1001 1002 1003 1004 MESSAGE LOGON MUST BE MANAGER.SYS,PUB.(DIRERR 1001) CAUSE The user is not logged on as MANAGER.SYS,PUB. ACTION The user should log on as MANAGER.SYS,PUB, and run DIRMIG.PUB.SYS again. MESSAGE THIS PROGRAM REQUIRES SYSTEM SUPERVISOR (OP) CAPABILITY. (DIRERR 1002) CAUSE The user does not have System Supervisor (OP) capability. ACTION The user should provide MANAGER.SYS,PUB with OP capability and run DIRMIG.PUB.SYS again. MESSAGE ALL JOBS AND SESSIONS MUST BE LOGGED OFF.
1005 1007 1016 G-88 1017 MESSAGE CURRENT LOGFILE SEQUENCE NUMBER EQUALS MAXIMUM SEQUENCE NUMBER ALLOWED (99) FOR DIRLOGnn .PUB.SYS. (DIRERR 1005) DIRMIG LOGGING FACILITY DISABLED. CONTINUE (YES/[NO]) ? >> CAUSE DIRMIG increments the current log le sequence number with each run. The sequence numbers range from 01 through 99. In this case, DIRLOG99.PUB.SYS exists on the system and DIRMIG is unable to increment the sequence number.
1018 MESSAGE UNABLE TO OBTAIN NATIVE LANGUAGE SUPPORT LANGUAGE ID. (DIRERR 1018) NLGETLANG INTRINSIC ERROR #n . NATIVE-3000 LANGUAGE ID WILL BE USED'' 1019 CAUSE DIRMIG calls the NLGETLAND intrinsic to obtain the user-interface language ID. This error usually occurs when the NLUSERLANG JCW is set to a language that is not con gured on the MPE/iX system.
1021 MESSAGE UNABLE TO REPLACE UNPRINTABLE CHARACTERS WITH '' (DIRERR 1021) NLREPCHAR INTRINSIC ERROR:#n . CAUSE DIRMIG calls the NLREPCHAR intrinsic to replace unprintable characters with a period ('.') within a string before the string is printed. NLREPCHAR is called before printing or logging a string suspected of being corrupt. Note: DIRMIG veri es strings of alphanumeric names such as RIN entries, user-logging identi ers, and all directory-related names before performing their migration.
1032 MESSAGE UNABLE TO DISPLAY MESSAGE:SET= set# ,MSG=msg# . (DIRERR 1032) CATREAD INTRINSIC ERROR:#n . CAUSE DIRMIG is unable to display the message desired because a read error occurred on the DIRMIG catalog le; the set or message number speci ed was not found in the le; or an internal message facility error occurred. ACTION The user should look up the indicated CATREAD intrinsic error in the Native Language Programmer's Guide (32650-90022) and troubleshoot accordingly.
1042 MESSAGE UNABLE TO OBTAIN VIRTUAL ADDRESS OF DST. (DIRERR 1042). CAUSE An MPE/iX internal error occurred while DIRMIG was trying to migrate system table information. ACTION The user should report the error message and MPE/iX status information to their Hewlett-Packard Support Representative. (logged only) 1043 MESSAGE UNABLE TO OBTAIN RIN TABLE SIR. (DIRERR 1043) CAUSE An MPE/iX internal error occurred while DIRMIG was trying to migrate system table information.
1046 2001 2002 2003 MESSAGE UNABLE TO RELEASE RIN TABLE SIR. (DIRERR 1046). CAUSE An MPE/iX internal error occurred while DIRMIG was trying to migrate system table information. ACTION The user should report the error message and MPE/iX status information to their Hewlett-Packard Support Representative. MESSAGE INVALID FILE SPECIFICATION FOR"MIGTAPE". (DIRERR 2001) UNABLE TO CONTINUE WITH MIGRATION.
2004 2005 MESSAGE MPE SYSDUMP TAPE IS NOT FROM AN MPE V/E-BASED SYSTEM. (DIRERR 2004) MIGRATION NOT POSSIBLE FROM THIS TAPE SET. CAUSE The MPE V/E SYSDUMP tape was generated on a system which is not running the appropriate MPE V/E-based software de ned as the base for migration to MPE iX. ACTION The user should update their system to the appropriate MPE V/E-based version and generate a new MPE V/E SYSDUMP tape to be used by DIRMIG.
2008 2009 MESSAGE ERROR OCCURRED WHILE CREATING DIRMIG TABLES. (DIRERR 2008) UNABLE TO CONTINUE WITH MIGRATION. REFER TO DIRLOGnn.PUB.SYS CAUSE DIRMIG was unable to allocate the temporary table space it required for the MPE global RINs or the MPE user-logging IDs. ACTION The user should check the indicated log le for the speci c error and refer to the action recommended for that error. Report the MPE/iX error information to your Hewlett-Packard Support Representative and troubleshoot accordingly.
3002 3003 MESSAGE MPE GLOBAL RINS NOT MIGRATED DUE TO CORRUPTION. (DIRERR 3002) REFER TO DIRLOGnn .PUB.SYS. CAUSE DIRMIG has detected the possibility of RIN table corruption. ACTION The MPE global RINs will not be migrated and DIRMIG will continue with the migration process. The user should check the indicated le for information on the corrupted entries.
4002 4003 MESSAGE MPE USER-LOGGING IDs NOT MIGRATED DUE TO CORRUPTION. (DIRERR 4002) REFER TO DIRLOGnn .PUB.SYS.'' CAUSE DIRMIG has detected the possibility of user-logging ID table corruption. ACTION The MPE V/E user-logging IDs will not be migrated and DIRMIG will continue with the migration process. The user should check the indicated le for information on the corrupted entries.
5002 5003 5004 5005 G-98 MESSAGE DIRECTORY MIGRATION NOT POSSIBLE DUE TO CORRUPTION. (DIRERR 5002) REFER TO DIRLOGnn.PUB.SYS. CAUSE DIRMIG has detected an invalid system directory pointer or a corrupted system account index block and is unable to migrate the directory. ACTION Refer to \Actions for MPE Directory Corruption", at the end of this appendix for the recommended action. MESSAGE UNABLE TO LIST ACCOUNT NAMES DUE TO DIRECTORY . CORRUPTION. (DIRERR 5003) REFER TO DIRLOGnn .PUB.SYS.
5006 5007 5008 MESSAGE n ERROR(S) FOUND WHILE LISTING ACCOUNT NAMES. CAUSE The user speci ed the option to list the MPE V/E account names obtained from the SYSDUMP tape. DIRMIG detects directory corruption and reports the total number of errors found. ACTION The user should check the current log le for the speci c directory errors logged and refer to the action recommended for each error. Contact your Hewlett-Packard Support Representative for assistance if necessary and troubleshoot accordingly.
5009 MESSAGE MPE/iX DIRECTORY ERROR DURING: directory routine . (DIRERR 5009) LOW STATUS: low status HIGH STATUS: hi status directory entry name DOES NOT EXIST. (DIRERR 5009) MIGRATION NOT SUCCESSFUL. CAUSE DIRMIG made a call to the MPE/iX system routine directory routine and the call failed. However, the directory was being migrated with the override option enabled and directory entry name was expected to exist in the directory and it did not.
6001 6002 MESSAGE PVASSIST.PUB.SYS MUST EXIST IN ORDER TO CONTINUE WITH PRIVATE VOLUME MIGRATION. (DIRERR 6001) CAUSE PVASSIST.PUB.SYS contains MPE V/E volume set ACTION User information only. Private volume migration is not necessary since the accounts migrated do not have volume sets. If the user wishes to perform private volume migration, run DIRMIG again and migrate those accounts with volume set information. MESSAGE INCOMPATIBLE VERSION NUMBER IN PVASSIST.PUB.SYS. FILE.
6003 MESSAGE CHECKSUM ERROR IN PVASSIST.PUB.SYS FILE. (DIRERR 6003) CAUSE DIRMIG performs an integrity check on PVASSIST.PUB.SYS and has detected a bad checksum. This may indicate a corrupted PVASSIST.PUB.SYS le. ACTION The user should purge PVASSIST.PUB.SYS and run DIRMIG again to recreate the le. To perform private volume migration for accounts which have already been migrated, run DIRMIG again and migrate the appropriate accounts specifying the override option.
6006 6007 MESSAGE ERROR OCCURRED WHILE MODIFYING PVASSIST.PUB.SYS. (DIRERR 6006) REFER TO DIRLOGnn .PUB.SYS. CAUSE The user has deleted a volume set, and a le system error occurred while DIRMIG was updating PVASSIST.PUB.SYS. PVASSIST may not have been updated to re ect the deleted volume set. ACTION The user should check the indicated log le for the le system message logged and troubleshoot accordingly.
6008 MESSAGE INCORRECT HOME VOLUME SET NAME FOUND FOR group.account . HOME VOLUME SET SHOULD BE vsetname . (DIRERR 6008) CAUSE This error is generated when a VOLUTIL command script is being generated for vsetname . The PVASSIST.PUB.SYS le indicates that the home volume set for group.account should be vsetname, but the PVASSIST entry for group.account shows a di erent home volume set name. This message indicates a problem with PVASSIST.PUB.SYS.
6051 MESSAGE UNABLE TO OBTAIN FILES LIMIT FOR GROUP group . DEFAULT FILES LIMIT USED. (DIRERR 6052) CAUSE DIRMIG obtains the disk le space limit for group by executing a :LISTGROUP command and redirecting the output to the temporary le, ACCTLIST.PUB.SYS. The group does not exist in the system directory or a le system error occurred while reading the information from the temporary le ACCTLIST.PUB.SYS . ACTION User information only.
7001 7002 7003 G-106 MESSAGE RESTORE OF COMMAND.PUB.SYS NOT SUCCESSFUL. (DIRERR 7001) REFER TO DIRLOGnn .PUB.SYS. CAUSE DIRMIG needs to restore COMMAND.PUB.SYS from the MPE SYSDUMP tape in order to proceed with UDC migration. It was unable to restore the le successfully because COMMAND.PUB.SYS was not on the tape or a RESTORE error occurred. ACTION DIRMIG logs the STOREJCW value after the restore is nished.
7004 7005 7006 MESSAGE RESTORE OF UDCFILES/ALL USER-FILES NOT SUCCESSFUL. (DIRERR 7004) REFER TO DIRLOGnn.PUB.SYS. CAUSE An error occurred while restoring UDC and/or user designated les. ACTION The current log le contains the STOREJCW value returned by the RESTORE process. Look up this value in the Performing System Operating Tasks (32650-90137) or the Controlling System Activity Reference Manual (32650-90155) and troubleshoot accordingly. DIRMIG will still proceed with UDC environment migration.
7007 7008 MESSAGE UNABLE TO ATTEMPT RESTORE OF UDC FILES/ALL USER FILES. (DIRERR 7007) REFER TO DIRLOGnn .PUB.SYS. CAUSE An error occurred while DIRMIG was creating UDCMASTR.PUB.SYS. the indirect le used when invoking STORE.PUB.SYS; or DIRMIG was unable to successfully create the STOREPUB.SYS process. ACTION The user should check the indicated log le for the speci c error and troubleshoot accordingly. DIRMIG will still proceed with UDC environment migration.
7020 7021 7022 MESSAGE UDC ENVIRONMENT MODIFICATIONS NOT SUCCESSFUL. (DIRERR 7020) REFER TO DIRLOGnn .PUB.SYS CAUSE While updating the MPE/iX directory to re ect new UDC le information in COMMAND.PUB.SYS, an error was returned from a call to an MPE/iX directory services routine.
7023 MESSAGE UNABLE TO OBTAIN MPE/iXUDC INFORMATION. (DIRERR 7023) CAUSE DIRMIG was unable to open, access, or obtain le characteristics for the MPE/iX COMMAND.PUB.SYS le. ACTION The user should check the current log le for the reason why the open or the access failed and troubleshoot accordingly. To migrate the UDC environment using DIRMIG, run DIRMIG again and perform directory migration with the override option.
7025 MESSAGE MPE/iX le system error message ERROR OCCURRED WHILE CAUSE Before the MPE V/E COMMAND.PUB.SYS is restored from the tape, DIRMIG saves the MPE/iX COMMAND.PUB.SYS le to SAVECMD.PUB.SYS. When DIRMIG is nished processing the information from the MPE V/E COMMAND.PUB.SYS le, it is purged and the original MPE/iX COMMAND.PUB.SYS is renamed back from SAVECMD via the FRENAME intrinsic. This message is logged if the FRENAME intrinsic fails.
7027 MESSAGE UNABLE TO BUILD A NEW MPE/iX COMMAND.PUB.SYS FILE. (DIRERR 7027) CAUSE DIRMIG was unable to create a new COMMAND.PUB.SYS le. An attempt is made to create a new COMMAND.PUB.SYS le when the migrating UDC environment information will not t in the existing COMMAND.PUB.SYS le due to le limit restrictions. ACTION DIRMIG will not proceed with UDC environment migrations for migrated accounts and users.
7030 MESSAGE UNABLE TO COPY ORIGINAL MPE/iX COMMAND.PUB.SYS BACK FROM COPYCMD.PUB.SYS. (DIRERR 7030) CAUSE DIRMIG was unable to copy the original MPE/iX COMMAND.PUB.SYS back from COPYCMD.PUB.SYS. While making modi cations to MPE/iX COMMAND.PUB.SYS, an error occurred. DIRMIG then attempts to restore the original MPE/iX UDC environment by copying back the original COMMAND.PUB.SYS.
7050 MESSAGE CANNOT FIND UDC FILES FOR USER user.account. NO UDC MIGRATION FOR THIS USER. (DIRWARN 7050) CAUSE DIRMIG searches the MPE V/E COMMAND.PUB.SYS le for UDC les to restore for each migrated user. This is done for those users who have UDC environment information in the MPE V/E COMMAND.PUB.SYS according to their MPE V/E directory entry. This message is displayed when DIRMIG is unable to nd UDC les for a migrated user who should have an entry in the MPE V/E COMMAND.PUB.SYS le.
Directory Corruption Error Messages Following is a list of directory corruption error messages returned by DIRMIG. The error text varies depending on the directory corruption identi ed and the logging messages displayed when the message is written to the DIRLOGnn le.
5020 MESSAGE CORRUPT MPE GROUP INDEX BLOCK PREFIX (DIRERR 5020): index block pre x error message (See below) DIRECTORY PATH. . . . ACCOUNT INDEX BLOCK PTR: sector location object name ACCOUNT ENTRY PTR: sector location object name GROUP INDEX BLOCK PTR: sector location object name GROUPS FOR account name NOT MIGRATED DUE TO CORRUPTION. CAUSE Refer to \Causes of MPE Directory Corruption". ACTION Refer to \Action for MPE Directory Corruption".
5020 MESSAGE CORRUPT MPE VSD/VCD INDEX BLOCK PREFIX (DIRERR 5020): vsd/vcd index block pre x error message (See Below) DIRECTORY PATH. . . . ACCOUNT|| INDEX BLOCK PTR: sector location object name ACCOUNT ENTRY PTR: sector location object name GROUP INDEX BLOCK PTR: sector location object name GROUP ENTRY PTR: sector location object name VSD/VCD INDEX BLOCK PTR: sector location object name VSDS/VCDS FOR group.account NOT MIGRATED DUE TO CORRUPTION. CAUSE Refer to \Causes of MPE Directory Corruption".
Depending upon the circumstances, one of the following messages will be appended to error message 5020 when DIRMIG writes the message to the logging le DIRLOGnn .
INDEX BLOCK INFO WORD. . . . BIT 0:1 MUST EQUAL 1, NOT 0. INDEX BLOCK INFO WORD. . . . ILLEGAL INDEX BLOCK ENTRY WORD SIZE. EXPECTED WORD SIZE = expected value , NOT existing value . INDEX BLOCK INFO WORD. . . . ILLEGAL IDENTIFIER EXPECTED IDENTIFIER = expected value , NOT existing value . INDEX BLOCK INFO WORD. . . . ILLEGAL INDEX BLOCK ENTRY SECTOR SIZE FOR THIS OBJECT TYPE (object type ). NUMBER SECTORS (existing value ) EXCEEDS NUMBER ALLOWED (expected value ).
5021 MESSAGE CORRUPT MPE ACCOUNT INDEX BLOCK ENTRY (DIRERR 5021): index block entry error message (See Below) DIRECTORY PATH. . . . ACCOUNT INDEX BLOCK PTR: sector location object name ACCOUNT ENTRY PTR: sector location object name CAUSE Refer to \Causes of MPE Directory Corruption". ACTION Refer to \Action for MPE Directory Corruption". (logged only) 5021 MESSAGE CORRUPT MPE GROUP INDEX BLOCK ENTRY (DIRERR 5021): index block entry error message (See Below) DIRECTORY PATH. . . .
5021 MESSAGE CORRUPT MPE VSD/VCD INDEX BLOCK ENTRY (DIRERR 5021): index block entry error message (See Below) DIRECTORY PATH. . . . ACCOUNT INDEX BLOCK PTR: sector location object name ACCOUNT ENTRY PTR: sector location object name GROUP INDEX BLOCK PTR: sector location object name GROUP ENTRY PTR: sector location object name VSD/VCD INDEX BLOCK PTR: sector location object name CAUSE Refer to \Causes of MPE Directory Corruption". ACTION Refer to \Action for MPE Directory Corruption".
5022 MESSAGE CORRUPT MPE ACCOUNT DIRECTORY ENTRY (DIRERR 5022): entry block entry error message (See Below) DIRECTORY PATH. . . . ACCOUNT INDEX BLOCK PTR: sector location object name ACCOUNT ENTRY PTR: sector location object name CAUSE Refer to \Causes of MPE Directory Corruption". ACTION Refer to \Action for MPE Directory Corruption". (logged only) 5022 MESSAGE CORRUPT MPE GROUP DIRECTORY ENTRY (DIRERR 5022): entry block entry error message (See Below) DIRECTORY PATH. . . .
5022 MESSAGE CORRUPT MPE VSD/VCD DIRECTORY ENTRY (DIRERR 5022): entry block entry error message (See Below) DIRECTORY PATH. . . . ACCOUNT INDEX BLOCK PTR: sector location object name ACCOUNT ENTRY PTR: sector location object nam GROUP INDEX BLOCK PTR: sector location object nam GROUP ENTRY PTR: sector location object nam VSD/VCD INDEX BLOCK PTR: sector location object name VSD/VCD ENTRY PTR: sector location object name CAUSE Refer to \Causes of MPE Directory Corruption".
within those blocks are used for migration. Corruption is assumed when values examined within those blocks do not match predetermined expected values. Often the values provide a check-and-balance of the directory structure. Other values are speci c to the type of block being examined, for example, values speci c only to the account index entry blocks.
users, groups, and volume set de nitions. If the directory is corrupt, LISTDIR5 output will re ect such symptoms. Contact your Hewlett-Packard Support Representative who may have access to tools to verify directory corruption. If it appears that the tape is bad, create a new tape and run DIRMIG again. Caution If it appears that the directory is corrupt do not attempt to x it. Contact your Hewlett-Packard Support Representative and describe the problem's symptoms.
H Notes On Migrating TurboIMAGE/V Database This appendix is intended for anyone responsible for migrating TurboIMAGE databases between an MPE V/E-based system and an MPE/iX-based system. This appendix is divided into the following subjects: \Migrating a TurboIMAGE/V Database to MPE/iX" explains some basic considerations about migrating a TurboIMAGE database from MPE V/E to MPE/iX and shows how to move a single database. Examples are provided to illustrate the migration of a database from MPE V/E to MPE/iX.
Migrating a TurboIMAGE/V Database to MPE/iX Migration of a database is a simple process and should take relatively little e ort in most cases. The process consists of performing a DBSTORE/DBRESTOR of each database you need to move from an MPE V/E-based system to an MPE/iX-based system. The most important step to remember prior to migration is identifying the databases which have Intrinsic Level Recovery (ILR) enabled. ILR should be disabled for a successful migration.
account. Use of the :STORE command is explained in the next section. 3. Mount the DBSTORE tape on the tape drive connected to the MPE/iX-based system and perform a DBRESTOR or RESTORE. An example of using DBRESTOR follows. An example of using the :RESTORE command is given in the next section. At this point, the basic migration is nished and the database can now be accessed. ILR does not need to be enabled to ensure database integrity. The use of ILR on MPE/iX is discussed in the next section.
d a :RUN DBSTORE.PUB.SYS <> HP32215C.00.24 TurboIMAGE/3000: DBSTORE (C) COPYRIGHT HEWLETT-PACKARD CO. 1978 WHICH DATA BASE? ORDERS <> STORE/RESTORE, VERSION 2 (C) 1981 HEWLETT-PACKARD CO.
d a :RUN DBRESTOR.PUB.SYS <> HP30391C.00.00 TurboIMAGE/iX: DBRESTOR (C) COPYRIGHT HEWLETT-PACKARD CO. 1987 WHICH DATA BASE? ORDERS <> STORE/RESTORE, VERSION 2 (C) 1981 HEWLETT-PACKARD CO.
Migrating a TurboIMAGE/XL Database Back to MPE V/E It may be desirable to move a database from an MPE/iX-based system back to an MPE V/E-based system. Moving back to an MPE V/E-based system is almost identical to the move from an MPE V/E-based system and will take about the same amount of time. Note that the TurboIMAGE/XL data set les must not exceed the MPE V/E le system limits.
The following examples show how the ORDERS database was migrated from an MPE/iX system back to an MPE V/E-based system. Example of Using d DBSTORE (MPE/iX) This example shows how ORDERS is stored to tape on an MPE/iX-based system. a :RUN DBSTORE.PUB.SYS:INFO="TRANSPORT" <> HP30391C.00.00 TurboIMAGE/XL: DBSTORE (C) COPYRIGHT HEWLETT-PACKARD CO. 1987 WHICH DATABASE? ORDERS <> Transport Store-Restore for MPE/iX, v. A.01.
d a :RUN DBRESTOR.PUB.SYS<> HP30391A.01.00 TurboIMAGE: DBRESTOR (C) COPYRIGHT HEWLETT-PACKARD CO. 1987 WHICH DATABASE? ORDERS<> STORE/RESTORE, VERSION A.01.00 (C) 1986 HEWLETT-PACKARD CO. WED,AUG 5, 1987, 9:56 AM WILL RESTORE 1 DATABASES; NUMBER OF FILES ON TAPE = FILES RESTORED: c 7 <> <<# of files>> Migrating Multiple Databases 7 The second method of migrating TurboIMAGE databases and applications is to use the STORE/RESTORE facility and DIRMIG.
4. Run the DIRMIG utility and specify the les and accounts you want recreated on the MPE/iX machine. 5. Perform a STORE of all the database les from the MPE V/E-based system and restore the les on the MPE/iX system. After completing the steps listed, you should have a duplicate of your MPE V/E directory, databases, and application programs installed on the MPE/iX system.
On the MPE/iX based system, TurboIMAGE uses the operating system services (transaction manager) to ensure that there are no broken chains in the database. The structural integrity of the database is preserved even if ILR is not enabled on MPE/iX. Enabling ILR in MPE/iX simply causes the operating system to ush some portions of memory to disk at the end of each DBPUT or DBDELETE. The result is that less work might be lost in the event of a system failure.
exception that the PB-o set of the CM stub is returned instead of the o set of the intrinsic. For NM programs the status array is not compatible, however the display for DBEXPLAIN is compatible. For TurboIMAGE/XL DBEXPLAIN merges the status array and RTCB values. However be aware that the RTCB values are valid only for the last intrinsic. Therefore, DBEXPLAIN must be called before any other TurboIMAGE/XL intrinsic to obtain the correct status array.
Data Alignment NM programs must use the HP 3000 compiler options. TurboIMAGE/XL data bu ers and internal data structures are still aligned on 16-bit boundaries.
I Using the Migration Planning Tool MPT is used in conjunction with its companion Migration Toolset utilities, RTM and OCA, during the analysis and planning stage of the migration e ort. MPT runs on MPE V/E-based systems. Included in this appendix are discussions on the following subjects: \Migration Planning Tool Operation" provides a general overview of MPT. This section is reference in nature.
\Evaluating Migration Planning Reports" describes the formats and contents of the six types of migration planning reports. This section is reference in nature. \Running the Migration Planning Tool in Batch Mode" provides instructions on how to use a provided job stream le to create the MPT database and generate reports. \Migration Planning Tool Program Error Messages" provides a comprehensive list of program error messages returned by MPT.
3. Generates six types of migration planning reports from information collected from the database. The reports contain information on: Disk capacity estimates for les migrating from an MPE V/E-based system to an MPE/iX-based system. Problem areas in les that may be encountered after the les are migrated to an MPE/iX-based system. MPT runs entirely on an MPE V/E-based HP 3000 Computer System in either interactive mode or batch mode.
Figure I-1 illustrates the major modules of MPT and how they work together to create the MPTDB database and to generate reports. Descriptions of each of the major modules follow. The following les are included in the Migration Planning Tool product: File Name Description MPTPROD.MPT.TELESUP The MPT program that identi es Hewlett-Packard products installed on the system. MPT.MPT.TELESUP The major data collection program for MPT. It scans each disk le found on the system for potential migration di culties.
MPTJOB.MPT.TELESUP reports from information collected from the MPTDB database. A job stream le that can be used to create the MPTDB database. It also generates several levels of migration planning reports and the installed products report.
I-6 Using the Migration Planning Tool Figure I-1.
Generating an Installed Products Report The MPTPROD program (MPTPROD.MPT.TELESUP) generates a report that enables you to identify Hewlett-Packard products installed on the system being analyzed. The purpose of this report is to alert you to the existence of products on your MPE V/E-based system. A full product integrity check is not actually performed for this report; rather, the system is checked to see if the proper les and system SL segments are present for each product.
Figure I-2. Sample MPT Installed Products Report The rst part of the report generated by MPTPROD lists Hewlett-Packard products that are fully installed on the system. A product is considered fully installed if all system SL segments unique to the product are found in SL.PUB.SYS and if the required disk les for the product (or a core set of them) are present on the system. The second part of the report generated by MPTPROD lists products that appear to be at least partially installed.
in SL.PUB.SYS and at least one of the required disk les is found. (It is possible that there are no required SL segments for this product). The % INSTALLED column is the percent of les required by the product actually found by MPTPROD. Note Creating the Migration Planning Tool Database Some Hewlett-Packard products have les which are purged as a part of the installation process. It is normal for these products to show up as less than fully installed. Products that are not installed are not listed.
To create the MPTDB database, follow the steps outlined below. Some of the steps are not required, but all must be considered:. 1. Run RTM: For details on using RTM, refer to Appendix C, \Using the Run Time Monitor". 2. Size the Database: In order to properly size the data sets in this database, MPT must know approximately how many disk les the database will hold. If the database is built too small, MPT or successive programs will abort with database errors.
Run the MPT.MPT.TELESUP program to create and load the MPTDB database used by MPT. Normally, MPT scans all disk les on the system including those on mounted and enabled private volumes. You can optionally limit the number of les scanned by MPT by using the INFO= parameter of the :RUN command to specify the MPE leset you want scanned. The following example executes the MPT program, specifying that only les in the ACCTING account are to be scanned: : RUN MPT.MPT.TELESUP;INFO="@.@.
ALL m,n MPTRTM scans through all log les found on the system. MPTRTM scans through the system log les numbered m to n . When RTM events are found recorded in the selected log les, they are entered into the MPTDB database. This concludes the data collection portion of MPT. You now use the MPTREPT program to generate migration planning reports.
You can encode user migration options for selected lesets into the special parameter le where the MPTREPT program can access it. The nal disk space will be calculated using your chosen mode for each le (instead of the default, CM). A parameter le, MPTOPTNS.MPT.TELESUP, is supplied by MPT and already contains a set of migration options you would probably use. To set or change the user migration options, use the text editor of your choice to modify MPTOPTNS.MPT.
TM= OT= Specify the Translated Mode le size in sectors. Specify the other mode le size in sectors. Actions can be one of the following: CM Migrate these les into CM. (This is the default.) NM Migrate these les into NM. TM Migrate these les into object code translation mode. OT Migrate these les into \other" (as yet unde ned). Delete Do NOT migrate these les to the MPE/iX system. Add Add a le to the MPE/iX system which does not already exist on the MPE V/E system.
Use CM disk space estimates when calculating nal disk space considerations for COBOL program les included in the report. Use NM disk space estimates when calculating nal disk space considerations for IMAGE les located in the account ACCTNG included in the report. Generating Migration Planning Reports You generate MPT migration planning reports after you have created and loaded the MPTDB database.
within accounts that might require more attention than others. Report Level Four (File Summary) lists each le that was agged as requiring migration attention . The number and severity of migration events is shown so you can pinpoint speci c les which need attention during migration. Report Level Five (File Detail) has the same information as Report Level Four plus a brief description of each migration event found in the le.
Follow the steps outlined below to generate MPT reports. Not all steps are required, but should be considered. 1. Select a User Options Parameter File: If you are using the MPTOPTNS parameter le (either your own, or the le MPTOPTNS.MPT.TELESUP supplied with MPT) to de ne migration options for disk space considerations, you must use the :FILE command to equate the MPT formal le designator MPTOPTNS to your parameter le. If you do not want user options de ned, you must equate MPTOPTNS to $NULL.
through the :RUN command to customize the report output generated by MPTREPT are: ,SAVEPAPER Eliminates page breaks at each major break in the report. (The default is a page break at major report breaks.) ;PARM=page length Selects the maximum number of lines printed on each page. The default is 60 lines per page. ;INFO=custom report title Prints the selected character string at the top of each report page. The supplied string can be a maximum of 60 characters.
4.1. Select Filesets to Include in Reports: The MPTREPT program rst prints a product banner to $STDLIST, then asks that you select the les to be included in the report, giving directions for including and excluding lesets from reports. At the following prompt, enter the lesets you want included (or excluded) from migration planning reports: ENTER FILESET: You can respond with one valid MPE leset per line. You can enter up to 100 lesets to be included and 100 lesets to be excluded (in any order).
Report levels 1 through 5 all use a common data extraction from the database, but report level 6 must extract its own data. If you desire only report 6 then you can save time by pressing 4CTRL5 4Y5 during the rst data extraction (before choosing a report) and terminating that extraction early. When report 6 is chosen it will extract its own data each time it runs.
4.3. Restrict Reported Events: If you select report level 4 or above ( le summary, le detail or event summary), you are further prompted to restrict the report by event severity .
Evaluating Migration Planning Reports Migration planning reports generated by the MPTREPT program provide information that will assist you in deciding upon the MPE/iX execution mode best suited for migrated MPE V/E program and SL les. MPE/iX provides two major modes of program execution: CM and NM. A third mode of program execution is provided through object code translation of MPE V/E program code.
only when going into NM. Others are, by their nature, uncertain in their di culty. The design philosophy of MPT is to report any problem, even if the chances of it causing a problem are very slight. In this way the user can check the event at their leisure before migrating to MPE/iX. A particular event may function properly when run in CM but not in NM. For this reason each event will be classi ed into one of the four severity levels both for CM and for NM.
WARNING ERROR at all, but they should be examined to be sure if migration is to be smooth. These events will not work on the new system without some modi cation. There is a work around or alternate method to accomplish the same task, but it might involve minor rework of the application. (For example, the :SYSDUMP command has been eliminated. You must use the SYSGEN utility instead. Also, the commands to SYSGEN are di erent from the interaction with :SYSDUMP .
obtained for information purposes (for example, stack size and code segment data) and will be included in the reports. Incompatibilities are generally caused by the program calling certain external procedures (or intrinsics) or by its use of Privileged Mode capability. SL RTM This category will result in a lot of POSSIBLE events, since it can detect that a procedure is called, but not what parameters are passed to it or what the application does with the results of that call.
RTM can be more speci c about an event than PROG events since it at least knows the parameters being passed. It still can't detect how an application uses the results of the routine so even many RTM events might not be actual problems. You may notice that the same event will be recorded as PROG and RTM. PROG says the application could call the routine in an incompatible way; RTM says it actually did. JOB UDC I-26 Using the Migration Planning Tool Note that RTM detects events only as they occur.
Selecting a Report Level The MPTREPT program allows you to generate six levels of migration planning reports and a general information summary that is generated each time a report is printed. The rst levels are general summaries about the system and might be used to gain a general understanding on the migration issues involved. Succeeding levels of reporting are designed to further isolate the reported migration events identi ed in les.
File Summary Report Level Four lists each le that was agged as requiring migration attention. The number and severity of migration events is shown so you can pinpoint speci c les which need attention during migration. You can minimize the relatively large amount of output generated by this level of report by excluding those accounts or groups you are not planning to migrate to an MPE/iX- based system.
Figure I-3.
Table I-1. MPTREPT General Information Summary Description. LINE# DESCRIPTION 1 An MPT banner that identi es the report level printed on the current page (in this example, \GENERAL INFORMATION"), a custom report title you can specify using the INFO= parameter of the :RUN command (in this example, :RUN MPTREPT.MPT.TELESUP; INFO= "Acme Rentals Inc."), and the current date.
System Summary Report Level One The System Summary Report Level One displays global migration information that may be present on your system. This report is printed each time you specify the value 1 in response to the ENTER THE LEVEL OF DETAIL YOU DESIRE (1-6) prompt of the MPTREPT program. The System Summary Report is a three-part report: Part One displays total numbers of migration events sorted by the various le types recognized by MPT.
Figure I-4.
Table I-2. System Summary Report Level One Description COLUMN LANGUAGE DESCRIPTION(Part One). The programming language for source, SL, and program les (for example, COBOL, FORTRAN, Pascal, or SPL). The following codes indicate further classi cation of the le in some cases, including: SOURCE Unclassi able program source les. STREAM ASCII les containing a job stream. TDP FILE Unprocessed TDP document les. UDC What MPT has interpreted to be ASCII UDC les. AUTO IMAGE automatic master data sets.
Part Two of the System Summary Report Level One displays a number of summary lines in a noncolumnar format. Figure I-5 is an sample of the second part of a System Summary Report Level One. Table I-3 describes the information returned in this part of the System Summary. Part Two Description. Figure I-5.
Table I-3. System Summary Report Level One Description (Part Two) LINE# DESCRIPTION 1 The total number of disk le descriptions included in this report (both those les examined in the MPTDB database and those les ADDed to the report). 2 The total number of SL and program les assigned Privileged Mode (PM) capability. 5 The average number of code segments obtained by averaging the number of code segments in each SL and program le on the system. 6 The number of bytes in an average-sized code segment.
Part Three of the System Summary Report Level One displays disk space requirements for each of the migration options sorted by both MPE V/E le codes and special codes interpreted by MPT. Figure I-6 is an sample of the third part of a System Summary Report Level One. Table I-4 describes the information returned in this part of the System Summary. Part Three Description. Figure I-6.
Table I-4. System Summary Report Level One Description (Part Three). COLUMN TYPE LANGUAGE DESCRIPTION The general MPE le type. This mnemonic comes from the le code (returned in LISTF,2 command). If the le code is zero, the following special interpretations are obtained by the analysis program: ASCII General character les. BINARY General binary data les. CIR Files of type Circular. MSG Files of type Message. RIO Files of type Relative Input/Output. KSAM Files of type KSAM.
Table J-4. System summary Report Level One Description (Part Three). COUNT The number of disk les of this type examined in this report. PERCENT OF TOTAL The percentage of the total disk space used that the disk les of this type will occupy on the MPE/iX-based system (based upon the migration option you selected in the MPTOPTNS parameter le). CM is the default. CHOSEN The disk space requirements for the disk les of this type based upon the migration option you selected in the MPTOPTNS parameter le.
Account Summary Report Level Two The Account Summary Report Level Two breaks down the migration information into account levels. The information returned in the Account Summary Report enables you to determine accounts that may be responsible for the majority of migration events or disk space. This report is printed each time you specify the value 2 in response to the ENTER THE LEVEL OF DETAIL YOU DESIRE (1-6) prompt of the MPTREPT program. Figure I-7 is a sample of a portion of an Account Summary Report.
Table I-5. Account Summary Report Level Two Description. COLUMN DESCRIPTION ACCOUNT The account name. # FILES The number of les selected in this account. COMPATIBILITY MODE The total number of CM migration events classi ed as \POSSIBLE" identi ed in the selected les in this account. POS COMPATIBILITY MODE The total number of CM migration events classi ed as \WARNING" identi ed in the selected les in this account.
Table J-5. Account summary Report Level Two Description. (Cont.) DATA STACK STACK The average initial stack size (in bytes) for all selected programs in this account. DATA STACK MAXDATA The average MAXDATA size ( in bytes) for all selected program les in this account. DISC SPACE MPE-V The MPE V/E disk space requirements (in megabytes) for all selected les in this account.
Group Summary Report Level Three The Group Summary Report Level Three is quite similar to the Account Summary Report Level Two, except that it summarizes by group rather than by account. This report is printed each time you specify the value 3 in response to the ENTER THE LEVEL OF DETAIL YOU DESIRE (1-6) prompt of the MPTREPT program. Figure I-8 is a sample of a portion of a Group Summary Report Level Three.
File Summary Report Level Four The File Summary Report Level Four provides summary information for each le selected for the report. This report displays the event number and severity level of all migration events located in each of the selected les. You can use the information returned in this report to pinpoint the les that need attention during migration. This report is printed each time you specify the value 4 in response to the ENTER THE LEVEL OF DETAIL YOU DESIRE (1-6) prompt of the MPTREPT program.
Table I-6. File summary Report Level Four Description. COLUMN TYPE LANGUAGE DESCRIPTION The general MPE le type. This mnemonic comes from the le code (returned in :LISTF,2 command). If the le code is zero, the following special interpretations are obtained by the analysis program: ASCII General character les. BINARY General binary data les. CIR Files of type Circular. MSG Files of type Message. RIO Files of type Relative Input/Output. KSAM Files of type KSAM.
Table J-6. File Summary Report Level Four Description. (Cont.) COMPATIBILITY MODE The total number of CM migration events classi ed as \POSSIBLE" identi ed in this le. POS COMPATIBILITY MODE The total number of CM migration events classi ed as \WARNING" identi ed in this le. WRN COMPATIBILITY MODE The total number of CM migration events classi ed as \ERROR" identi ed in this le. ERR NATIVE MODE POS The total number of NM migration events classi ed as \POSSIBLE" identi ed in this le.
Table J-6. File Summary Report Level Four Description. (Cont.) AC I-46 This eld indicates when a migration option (action) has been \Chosen" for this le. The default action is to migrate the le into CM and will show up as a blank in this eld.
File Detail Report Level Five The File Detail Report Level Five returns information about the migration events detected for a le, in addition to the information contained in the File Summary Report Level Four (described in Table I-6). This report is printed each time you specify the value 5 in response to the ENTER THE LEVEL OF DETAIL YOU DESIRE (1-6) prompt of the MPTREPT program. Figure I-10 is a sample of a portion of a File Detail Report Level Five. Figure I-10.
The migration event type and unique identifying number is given (example: PROG ERR# 106). The event type identi es what type of event scanning detected the event. Possible events and their sources are described earlier in this document. The ERR# indicates a unique migration event. You may look up the event number in Appendix D, \Incompatibilities" to determine more information about what causes the event, how to tell if it is signi cant, and what corrective action can be taken if needed.
The number of times the event occurred is listed. For RTM events, this is the actual number of times the event was detected and logged while RTM was enabled. For most other events, this number will be one. The exception to this rule is where more than one routine can cause the same event message. For example, calling a system routine that is marked as \uncallable" (it requires the calling program to be in Privileged Mode to make the call) will generate a migration event.
Event Detail Report Level Six The Event Detail Report Level Six is unlike the other reports generated by MPTREPT in that the information in the report is sorted by migration event, not by le, leset, group, or account. This report lists each migration event that occurred in the selected les, followed by all the les in which that event was found. In this way it should be simple to locate the les which need to be modi ed.
Figure I-11.
Running the Migration Planning Tool in Batch Mode Customizing the MPTJOB Job Stream File Part of the MPT product is a job stream le, MPTJOB.MPT.TELESUP , that you can use to create the MPTDB database and generate the installed products report as well as report levels 1, 2, 3, and 6 of migration planning reports for all les located on the system being analyzed. If you want to customize the reports produced by MPTJOB, you have to modify the program using a text editor.
Note The job stream attempts to log on as MANAGER.SYS because the MPT program requires SM capability in order to scan all les on the system. Progress reports will be sent to the console during the job execution.
Migration Planning Tool Program Error Messages MPTPROD Program Error Messages I-54 The error and warning message listed in the following four tables are generated by the four programs that make up the MPT product. The error and warning messages listed below may result when running the MPTPROD program. Any of these errors may indicate some problems with the MPTPROD program, the MPT message catalog, or the MPTPARMS parameter le.
3 10 MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION 11 MESSAGE CAUSE ACTION UNABLE TO OPEN THE PRODUCTS FILE (MPTPARMS). The FOPEN intrinsic failed. Be sure that the MPTPARMS le has been localized using the appropriate le equation. MPTPROD expects the le to be in the same group in which it is executing. For further information, refer to the Migration Process Guide (30367-90007) for details. If the problem cannot be resolved, please contact a Hewlett-Packard Support Representative.
MPT Program Error Messages I-56 The error and warning messages listed below may result when running the MPT program. Any of these errors may indicate some problems with the MPT program, the MPT message catalog, or the MPTPARMS parameter le.
3 MESSAGE CAUSE ACTION 10 11 12 UNABLE TO CREATE SON PROCESS (CREATEPROCESS ERROR errornumber ). The CREATEPROCESS intrinsic failed. Refer to the Migration Process Guide (30367-90007) for details. If the problem cannot be resolved, contact a Hewlett-Packard Support Representative. Include all information listed by the MPT program. MESSAGE CAUSE ACTION OPEN ERROR errornumber ON SL FILE lenumber . MESSAGE CAUSE ACTION READ ERROR errornumber ON SL FILE lenumber .
13 14 15 17 MESSAGE CAUSE ACTION READ ERROR errornumber ON PROGRAM FILE lenumber . MESSAGE CAUSE ACTION OPEN ERROR errornumber ON ASCII FILE lenumber . MESSAGE CAUSE ACTION READ ERROR errornumber ON ASCII FILE lenumber . MESSAGE CAUSE ACTION 19 I-58 MESSAGE CAUSE The FOPEN intrinsic failed to open an SL le. Refer to the Migration Process Guide (30367-90007) for details. If the problem cannot be resolved, please contact a Hewlett-Packard Support Representative. The FOPEN intrinsic failed.
21 MESSAGE CAUSE ACTION 28 MESSAGE CAUSE ACTION 33 42 43 MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION NO INTRINSICS WERE FOUND IN THE 'MPTPARMS' FILE. NO PROGRAM FILE INCOMPATIBILITIES CAN BE FLAGGED BUT THE FILE SCANNING WILL CONTINUE ANYWAY. MPT reached the end of the le and failed to locate the $INTRINSICS section. Make sure the $INTRINSICS section of the MPTPARMS le was included on the original product tape. If not, please contact a Hewlett-Packard Support Representative.
44 45 47 48 50 MESSAGE CAUSE ACTION The FREEDSEG intrinsic failed. Please contact a Hewlett-Packard Support Representative. MESSAGE CAUSE TOO MANY DATABASE ERRORS HAVE OCCURRED (> maxerrors). ACTION Refer to the IMAGE Data Base Management System Reference Manual (32215-90003) or TurboIMAGE Data Base Management System Reference Manual (32215-90050) for information. If the problem cannot be resolved, please contact a Hewlett-Packard Support Representative.
51 52 53 MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION 54 55 MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION ERROR OCCURRED WHILE READING THE $STDLIST FILE. The FREAD intrinsic failed. Refer to the Migration Process Guide (30367-90007) for details. If the problem cannot be resolved, please contact a Hewlett-Packard Support Representative. ERROR OCCURRED WHILE WRITING TO THE $STDIN FILE. The FWRITE intrinsic failed. Refer to the Migration Process Guide (30367-90007) for details.
56 MESSAGE CAUSE ACTION INVALID ENTRY IN THE 'FCODE' INFORMATION (NO FCODE"=" PARAMETER). The format for one of the le codes in the $FCODE section of the MPTPARMS le is invalid. Check the MPTPARMS le for errors in the le code formats. Make sure the $FCODE section of the MPTPARMS le consists of entries in the following format: PROG = 1029 SL = 1031 . . . FCODE = parameter Contact a Hewlett-Packard Support Representative for the proper le code information.
60 MESSAGE CAUSE ACTION 61 MESSAGE CAUSE ACTION 62 63 64 MESSAGE CAUSE ACTION ??????? ROOT FILE IS INVALID (nnn) This error occurs on non-TurboIMAGE databases. MPT does not recognize the IMAGE version that created this root le, or the maximum root length (the number of items or number of sets) has been exceeded. MPT cannot analyze the database associated with this root le. Please contact a Hewlett-Packard Support Representative. ERROR ON MOVING DATA TO EXTRA DATA SEGMENT.
MPTRTM Program Error Messages I-64 The error and warning messages listed below may result when running the MPTRTM program. Any of these errors may indicate some problems with the MPTRTM program, the MPT message catalog, the MPTDB database, or the MPTPARMS parameter le.
2 8 9 MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION 13 MESSAGE CAUSE ACTION UNABLE TO OPEN THE 'MPTDB' DATABASE. The DBOPEN intrinsic failed. Be sure the MPTDB has been localized properly by using the appropriate le equations. If this does not solve the problem, check to see if you have the appropriate capabilities to access the database. The SM capability is required. Check to see if the database has been created. If not, run MPT to create it.
14 17 19 I-66 MESSAGE CAUSE ACTION ATTEMPT TO ADDRESS OUT OF BLOCK. MPTRTM is currently analyzing a bad system log le. None. The problem is not an MPTRTM program error. MESSAGE CAUSE ACTION MISSING LOG FILES LOGnnnn to LOGnnnn MESSAGE ACTION SORRY, THE DISC BLOCK SIZE IS TOO BIG (> maxsize) . The FOPEN intrinsic failed to open the log les. The log les are not on the system. If the log les are on the system, please contact a Hewlett-Packard Support Representative.
MPTREPT Program Error Messages The error and warning messages listed below may result when running the MPTREPT program. Any of these errors may indicate some problems with the MPTREPT program, the MPT message catalog, the MPTPARMS parameter le, or the MPTOPTNS user option le.
2 4 7 15 I-68 MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION MESSAGE CAUSE ACTION UNABLE TO OPEN THE 'MPTDB' DATABASE. The DBOPEN intrinsic failed. The MPTDB database must be present on the system. If it is not, build it by running MPT. If the database is present, make sure the appropriate le equations are set up.
27 MESSAGE CAUSE ACTION 29 MESSAGE CAUSE ACTION 33 MESSAGE ACTION THERE IS NO "=" FOLLOWING THE COMMAND commandname (COMMAND IGNORED). An equal sign is missing in the MPTOPTNS le. Edit the MPTOPTNS le and place an equal sign after the reported command. YOU CAN'T ADD A FILE WITHOUT SPECIFYING THE 'FNAME' PARAMETER. MPTREPT did not nd the lename in the correct format in the MPTOPTNS le. Edit the MPTOPTNS le and enter \FNAMES=" in front of the speci ed lename. TOO MANY FILE CRITERIA WERE FOUND.
Index A B C account structure, 4-3 ALLBASE/SQL, 2-15 ALTACCT command, D-4 ALTGROUP command, D-4 ALTVSET command, D-56 analysis and planning stage, 1-4, 3-1{17 analysis stage, 1-4 APL command, D-56 application migration, 3-1, 3-11, 4-2, B-2, C-2 ARITRAP intrinsic, D-12 ASOCTABL program, D-58 ASOCTBL# program, D-60 backward compatibility, A-1{2 CACHECONTROL command, D-17, D-40 CM application migration, 2-11{12 backward compatibility, A-1 compilers, 2-12, 6-1 environment, 2-4 operation, 1-7 SLs, 2-13 subsys
ALTACCT, D-4 ALTGROUP, D-4 ALTVSET, D-56 APL, D-56 CACHECONTROL, D-17, D-40 COBOL, D-56 COBOLGO, D-58 COBOLPREP, D-58 DBRESTOR, 2-17, H-3 DBSTORE, 2-17, H-2, H-6 DISCRPS, D-40 DSCONTROL, D-19, D-52 EOF, D-56 FOREIGN, D-52 FULLBACKUP, D-40 GIVE, D-54 LISTACCT, D-13, D-46 LISTF, D-13, D-50 LISTFTEMP, D-52 LISTGROUP, D-15, D-46 LISTUSER, D-15, D-46 LISTVS, D-54 MPLINE, D-54 NEWACCT, D-4 NEWGROUP, D-4 NEWVSET, D-54 PARTBACKUP, D-42 PREP, D-50 PTAPE, D-15, D-42 PURGEACCT, D-4 PURGEGROUP, D-4 PURGEVSET, D-56 QUAN
STOPCACHE, D-17, D-44 SYSDUMP, D-44 TAKE, D-54 TUNE, D-15, D-44 VINIT, D-46 compilers, 2-9, 2-12, 4-1, 6-1 compilers in CM, 2-12 CREATEPROCESS intrinsic, D-10 CS data communications, D-38 D data alignment, 2-8{9, 2-21 database migration, 2-15, 4-2, H-1{12 data capture, D-38 data communications CS, D-38 migration, 2-10{11 PTOP, D-38 RFA, D-38 DBCONV utility, 2-21 DBEnvironments, migration steps, 2-15 DBRESTOR, 2-16 DBRESTOR command, 2-17, H-3 DBSTORE, 2-16 DBSTORE command, 2-17, H-2, H-6 DEL screen handling
veri cation, G-64 with dialog, G-14 without dialog, G-12 DISCRPS command, D-40 DISKED# program, D-46 disk space with RTM, C-6{7 DPAN# program, D-50 DS/3000, 2-10, 4-2 DSCONTROL command, D-19, D-52 E F Index-4 education stage, 1-3, 2-3 emulator, 2-4 EOF command, D-56 error messages DIRMIG, G-82 GETUDC, F-7 MPT, I-54{69 OCA, B-49{58 RTM, C-24{27 event classi cations, C-2 FastLane 3000, 2-20 FCARD intrinsic, D-36 FCONTROL intrinsic, D-36 FDEVICECONTROL intrinsic, D-36 FFILEINFO intrinsic, D-22, D-24, D-26,
G H I GENMESSAGE intrinsic, D-10 GETPRIVMODE intrinsic, D-40 GETUDC, 4-4, F-1{12 error messages, F-7 HELP, F-3 indirect les, F-3 operation, F-1 prompts, F-3, F-6 start up, F-3 GIVE command, D-54 HP 3000 oating point, 2-9 HP 3000 system overview, 2-3 HPFPCONVERT intrinsic, 2-10, 2-21 HPGETPROCPLABEL intrinsic, D-12 HP-PA, 2-3 HP SQL, 2-15 IEEE oating point, 2-9 ILR, H-2 incompatibilities, 1-4, 3-2, 3-3, 3-8, 3-11, D-1{64 undetected, D-2 indirect le, B-8 installation stage, 1-7, 5-1{4 intrinsics ARITRAP, D
iXIBTRAP, D-8 LOADPROC, D-12 MYCOMMAND, D-10 PTAPE, D-36 SEARCH, D-8 STARTSESS, D-38 SWITCHDB, D-12 VBLOCKREAD, E-21 VBLOCKWRITE, E-18 VGETIEEELONG, E-8 VGETIEEEREAL, E-6 VPUTIEEELONG, E-12 VPUTIEEEREAL, E-10 VTURNOFF, E-14 VTURNON, E-16 XARITRAP, D-8 XCONTRAP, D-8 XSYSTRAP, D-8 introduction, 1-1 iX, 2-14 iXIBTRAP intrinsic, D-8 K L Index-6 KSAM le system, D-38 language conversion utilities, 2-21 LinkEditor, 2-12 LISTACCT command, D-13, D-46 LISTDIR# program, D-46 LISTEQ# program, D-48 LISTF command, D-1
M MEMLOGAN program, D-58 MEMTIMER program, D-48 migrating TurboIMAGE, 2-16 migration applications, 3-1, 3-11, 4-2, B-2, C-2 compilers, 4-1 database, 2-15, 4-2, H-1{12 data communications, 2-10 directories, 4-3 global RINs, 4-4 incompatibilities, 1-4, 3-2, 3-3, 3-8, 3-11 operating environment, 2-8, 5-2 performance enhancement, 2-14, 2-15 peripherals, D-1 phased, 2-6 private volumes, 5-3 project team, 2-1 SPL programs, 2-13 stages of, 1-1 strategies, 1-5, 2-7{8, 3-9, 3-12, 3-13 tools, 2-20, 3-2 UDCs, 4-3, 4-
installed products report, I-7{9 tasks, I-2 with RTM, I-3 MYCOMMAND intrinsic, D-10 N O Index-8 NEWACCT command, D-4 NEWGROUP command, D-4 NEWVSET command, D-54 NM application migration, 2-12{13 compilers, 2-9, 2-12 environment, 2-4, 2-5 iXs, 2-14 operation, 1-8 NS3000, 2-10, 4-2 OCA, 2-20, 3-5{6, 3-8, B-1 error messages, B-49{58 ow of control, B-4 HELP, B-4 in batch mode, B-28{29 indirect le, B-8 prompts, B-6, B-7, B-9, B-11, B-13, B-19 reports, B-2, B-18{19, B-25{27, B-30{48 run instruction, B-4 run op
P PARTBACKUP command, D-42 Pascal, D-5 peripherals, D-1 phased migration, 1-5, 2-6, 2-11 phased migration of databases, 2-15 pipelining, 2-3 planning stage, 1-5, 3-13{17 preparation stage, 1-6, 4-1{5 PREP command, D-50 private volume migration, 5-3 procedures MPE, D-40 SL, 2-13, D-60, D-62, D-63 THISCPU, D-40 uncallable, D-62 programs ASOCTABL, D-58 ASOCTBL#, D-60 DISKED#, D-46 DPAN#, D-50 FREE5, D-46 LISTDIR#, D-46 LISTEQ#, D-48 LISTLOG#, D-48 MEMLOGAN, D-58 MEMTIMER, D-48 OPT, D-50 RECOVER#, D-48 SDCONV,
Q R S Index-10 QUANTUM command, D-50 RECOVER# program, D-48 REPORT command, D-4 reports MPT, I-7{9, I-15{51 OCA, B-2, B-18{19, B-25{27, B-30{48 RTM, C-4, C-18{23 RFA data communications, D-38 RINs, 4-4 RISC, 2-3 RTM, 2-21, 3-6{7, 3-8, C-1 disk space, C-6{7 error messages, C-24{27 event classi cations, C-2 ow of control, C-10, C-19 HELP, C-18 in batch mode, C-14{17 prompts, C-12{14 reports, C-4, C-18{23 stack space, C-5{6 start up, C-8{12 system logging, C-2 termination, C-14 screen handling DEL, D-38 SD
with RTM, C-5{6 STARTCACHE command, D-17, D-42 STARTSESS command, D-19 STARTSESS intrinsic, D-38 STOPCACHE command, D-17, D-44 SWAT, 2-14, 2-21 SWITCHDB intrinsic, D-12 Switch subsystem, 1-8, 2-5, 2-13, 2-14 SYSDUMP command, D-44 system logging, D-7 with RTM, C-2 system overview, 2-3 T U TAKE command, D-54 test plan, 6-2 THISCPU procedure, D-40 tools, 1-3, 2-20{22, 3-2 DIRMIG, 2-8, 4-3, 4-4, 5-1{4, G-1{125 FastLane 3000, 1-5, 2-20 GETUDC, 4-4, F-1{12 MPT, 3-4{5, 3-7, 3-8, I-1{69 OCA, 3-5{6, 3-8, B-1 OCT,
V X Index-12 VBLOCKREAD intrinsic, E-21 VBLOCKWRITE intrinsic, E-18 VGETIEEELONG intrinsic, E-8 VGETIEEEREAL intrinsic, E-6 VINIT command, D-46 VPLUS, E-1{24 Call Intrinsic, E-4 data alignment, E-3 non-VPLUS I/O, E-5 Pascal integers, E-2 real data types, E-3 terminal refresh, E-3 terminals, E-1{2 type ahead, E-3 VPUTIEEELONG intrinsic, E-12 VPUTIEEEREAL intrinsic, E-10 VTURNOFF intrinsic, E-14 VTURNON intrinsic, E-16 XARITRAP intrinsic, D-8 XCONTRAP intrinsic, D-8 XSYSTRAP intrinsic, D-8
