Open System Services Porting Guide (G06.29+, H06.06+, J06.03+)

Some Guardian procedure calls have been replaced in the native environment:
• SIGACTION_INIT_ supersedes ARMTRAP.
• CHECKPOINTX supersedes CHECKPOINT.
• CHEKPOINTMANYX supersedes CHECKPOINTMANY.
• CURRENTSPACE is obsolete and has no replacement.
• ADDRESS_DELIMIT_ supersedes LASTADDR and LASTADDRX.
• SIGACTION_SUPPLANT_ supersedes SETTRAP.
For details on Guardian procedures, refer to the Guardian Procedure Calls Reference Manual. For
details on migrating to the TNS/R and TNS/E native environments, refer to the TNS/R Native
Application Migration Guide and the H-Series Application Migration Guide.
TAL to pTAL Conversion
pTAL (portable Transaction Application Language) replaces architecture-specific TAL constructs
with new constructs. pTAL source code can be compiled with the pTAL compiler or with the D30.03
and D40 TAL compilers. There are two pTAL compilers: one for the TNS/R native environment and
one for the TNS/E native environment. The two compilers are nearly identical, except that they
generate object code specific to their respective environments.
There are significant benefits to using pTAL instead of TAL. pTAL code runs faster than TAL code,
and using the pTAL compiler is faster than using the TAL compiler and the Accelerator or Object
Code Accelerator program. pTAL code can be used in an OSS program in the native environments,
provided that the main() function is in a C language file.
TAL source code may be processed with a pTAL compiler syntax checker option. This helps identify
most conversion issues, expands DEFINEs in error messages, and flags errors at statement and
declaration lines.
For detailed information about the pTAL language and conversion issues, refer to the pTAL
documentation listed in “Related Information” (page 18).
TAL to pTAL Conversion 177