HP 3000 Manuals HP 3000 Manuals
Features that Differ Between Transact/V and Transact/iX The following features differ in usage or in effect between Transact/V and native mode Transact/iX: * Multiple systems in one file * Parameters passed by value or by reference in the PROC verb * Parent and child values in SET(UPDATE)[REV BEG] * ALIGN option of LIST and PROMPT verbs * Fill characters used for data type 9 with the MOVE verb[REV END] Multiple Systems in One File The Transact/V compiler creates a separate p-code file for each SYSTEM statement in a source file. The native mode Transact/iX compiler creates a single RSOM file regardless of how many SYSTEM statements are in a source file. The first system is compiled as a main program and the remaining systems are compiled with the SUBPROGRAM option. If the SUBPROGRAM option is provided in the INFO string when running the native mode Transact/iX compiler, all systems in the source file are compiled with the SUBPROGRAM option. (See "Transact/iX Compiler Options" in Chapter 9.) Parameters Passed by Value or by Reference in the PROC Verb Transact/V does not do type checking on passed parameters. Transact/iX checks the calls to system intrinsics to verify that reference parameters and value parameters are passed as expected. For more information see the PROC verb in Chapter 8. Parent and Child Values in SET(UPDATE) In Transact/V, if a parent-item value is placed in the update register before a child-item value, the parent value overrides the child value. In Transact/iX, however, the child value overrides the parent value. [REV BEG] ALIGN Option of LIST and PROMPT Verbs. [REV END] In Transact/V, alignment is on 16-bit word boundaries. In MPE/iX, alignment is on 32-bit word boundaries. Fill Characters Used for Data Type 9 with the MOVE Verb Null is the fill character used for the 9 data type in a Transact/V MOVE. In a Transact/iX MOVE, the fill character is blank.