GDSX (Extended General Device Support) Manual

Design and Development
Extended General Device Support (GDSX) Manual—529931-001
2-44
Compiling
For example, you could create the following UBUILD file:
Comment*********************************************************
Comment * UBUILD Build Example USCODE from USAMPLE (16Mar93) *
Comment * Aded a compilation step to create USCODE2 (03Feb05) *
Comment*********************************************************
Clear All
Comment Assign SSV1 TO GDSX volume.subvolume
Comment for ULHDECS, DCCBDECS, ZGDXTAL, PEXTGDS and USAMPLE
Assign SSV1,< vol>.< subvol>
Comment
Comment ASSIGN SSV2 TO EXTDECS0 location
Assign SSV2,$System.System
Comment
Comment ASSIGN SSV3 TO SPI subvolume for ZCOMTAL, ZSPITAL
location
Assign SSV3,$System.Zspidef
Comment
Tal /In Usample,Mem
64/uscode;Symbols,Inspect,NoCode,NoIcode,NoMap
Clear All
Comment Compilation Step to create USCODE2
Tal /In Usample2,Mem
64/uscode2;Symbols,Inspect,NoCode,NoIcode,NoMap
Clear All
Comment Compilation Step to create USCODE2
Tal /In Usample2,Mem
64/uscode2;Symbols,Inspect,NoCode,NoIcode,N
oMap
Clear All
In this example, the user code file is named USKEL1, and the object file is named
USCODE. An OUT file is used to capture the compile listing. If your program has
been converted to run at a high PIN, you can set the HIGHPIN object-file attribute with
the following statement:
> TAL /IN USKEL1, MEM 64, OUT $S.#USKEL1/ USCODE; HIGHPIN
After creating UBUILD, issue the command OBEY UBUILD to compile the source code
file and produce the object file.