Code the SIP deck

z/TPF provides a set of SIP macros that are used to define the system configuration. These macros are coded in an assembler source file, known as the SIP deck. See Coding the SIP macros for more information about how to code these macros.

Table 1 describes how the HFS and PDS names are affected by the coding of the SSDEF macro for the four basic types of supported configurations.
Table 1. SIP deck coding
System type SSDEF macro parameters GENSIP macro parameters
PDSNAME=

(See table note 1.)

 TPFROOT=
Base only, configured system Not applicable. TPF,Z11.BAS, where .BAS is an optional qualifier. /tpf/z11/bas
Basic subsystem BSSGEN=YES (SSNAME defaults to BSS) TPF,Z11.BSS, where .BSS is an optional qualifier. /tpf/z11/bss
Named basic subsystem
  • BSSGEN=YES
  • SSNAME=xxxx, where xxxx is a 2- to 4-character alphanumeric basic subsystem name.
 TPF,Z11.xxxx, where xxxx is an optional 2- to 4-character alphanumeric basic subsystem name. /tpf/z11/xxxx, where xxxx is a 2- to 4-character alphanumeric basic subsystem name. (See table note 3.)
Subsystem
  • BSSGEN=NO
  • SSNAME=yyyy, where yyyy is a 4-character alphanumeric subsystem name.
  • BSSNAME=xxxx, where xxxx is a 4-character alphanumeric basic subsystem name. If omitted, the default value is BSS.
 TPF,Z11.xxxx, where xxxx is an optional 2- to 4-character alphanumeric basic subsystem name, which must be the same as the basic subsystem name that is specified using the PDSNAME parameter. /tpf/z11/yyyy, where yyyy is a 2- to 4-character alphanumeric subsystem name. (See table note 3.)
Note:
  1. The PDS names are not affected by the SSDEF macro.
  2. If you add your own format-1 globals definitions to the SIP deck, you will also need to make corresponding updates to the default format-1 globals macro and header files that are generated by the bldtpf -sip command. See the man page on Linux® for information about the bldtpf -sip command. See the following for additional information about format-1 globals:
  3. The directory name must be lowercase.

You can code COPY statements in the SIP deck so that the SIP macros can be grouped into different copy segments.

It is recommended that you place the SIP deck in the file /tpf/z11/sys/src/sip.asm, where sys is a lowercase value that corresponds to the value specified with the SSNAME parameter of the SSDEF macro. For example, if you are building:
  • A base-only system using the default name, sys is bas
  • A basic subsystem using the default name, sys is bss
  • A subsystem named ss1, sys is ss1.
The system configuration dependent source code (such as macros and include statements) generated later in the build is written to the same sys directory. In the examples that follow, the SIP deck referenced is stored under the /tpf/z11/bss/src/sip.asm file.

See /tpf/z11/base/samples/sip/sip.asm for a sample SIP deck.