CRE Programmer's Guide

Common Language Utility (CLU) Library Functions
Common Run-Time Environment (CRE) Programmer’s Guide528146-004
9-39
TAL Considerations
result = SMU_Assign_GetValue_ (messagenumber, portion, value)
result = GetAssignValue (portion, value, messagenumber)
result = SMU_Assign_PutText_ (messagenumber, portion, text)
result = PutAssignText (portion, text, cplist, messagenumber)
result = SMU_Assign_PutValue_ (messagenumber, portion, value)
result = PutAssignValue (portion, value, cplist,
messagenumber)
result = SMU_Param_Delete_ (portion)
result = DeleteParam (portion, cplist)
result = SMU_Param_GetText_ (portion, text)
result = GetParamText (portion, text)
result = SMU_Param_PutText_ (portion, text)
result = PutParamText (portion, text, cplist)
result = SMU_Startup_Delete_ (portion)
result = DeleteStartup (portion, cplist)
result = SMU_Startup_GetText_ (portion, text)
result = GetStartupText (portion, text)
result = SMU_Startup_PutText_ (portion, text)
result = PutStartupText (portion, text, cplist)
result = SMU_Assign_CheckName_ (name)
result = CheckLogicalName (name)
result = SMU_Message_CheckNumber_ (messagenumber)
result = CheckMessage (messagenumber)
TAL Considerations
TAL routines can use the new SMU functions if the TAL routines are part of a program
that can run in the TNS CRE or part of a program that can run in a COBOL or
FORTRAN run-time environment. TAL routines cannot use the old SMU functions.
The file CLUDECS, which is usually in the $SYSTEM.SYSTEM subvolume, contains
the new SMU function declarations.
All other usage considerations applicable to TAL are included in the function
descriptions in this section.
EpTAL Considerations
EpTAL-compiled routines can use the current SMU functions if the EpTAL routines are
part of a program that can run in the TNS/E native CRE (for example, a program that
has its main routine written in C instead of pTAL). EpTAL-compiled routines cannot use
the pre-D20 SMU functions.