gtps4m3cSystem Generation

SYNCLK

The SYNCLK macro is used to specify the synchronous link control (SLC) routing tables and features of the SLC network. It is only required when SLC line discipline is used by the generated system (SLCAI parameter in LINES macro does not equal zero).

The SYNCLK macro is only to be coded when generating a base only system or when generating the basic subsystem in a multiple database function (MDBF) environment.

See macro CTKL in TPF System Macros for coding instructions of the link and channel keypoints for synchronous link control support. See TPF Non-SNA Data Communications Reference for more information about synchronous link control.

Format




Notes:

  1. Up to 50 items may be entered, one item per remote interchange.

(a,b,c,d,e,f)
These fields make up the SLC routing table. Up to 50 items may be entered, one item per remote interchange.

a
Symbolic link number (SKN) for this entry. The SKN should be submitted as a two-digit decimal number relative to the first SLC line in the system. (e.g., the first SLC line = 01, the third = 03, etc.) The SKN relative line number will be converted to an actual symbolic line number. This number must not exceed the number of SLC lines submitted in LINES (SLCAI).

b
High level exit address (HEX) associated with this remote interchange address in hex. Value is a 4-digit entry with each character not greater than 7F (maximum value = 7F7F).

c
Terminal Circuit ID (TCID) for this entry in 2-character hex. Value must not exceed 7F.
Note:
The TCID identifies the circuit out of the high level center to which the remote interchange is attached.

d
Pseudo-line number (PLN) for this entry. PLN is handled exactly as SKN. Decimal value must not exceed number of pseudo-lines entered in LINES (PSLNS).

e
Interchange address (TIA) on the PLN in 2-character hex. Value must not exceed 3F.

f
Data translate code (IND) used for the PLN. The translate code must be one of the following:

PSB
Padded Sabre (ALC)

PBT
Padded Baudot

ISO
International Standards Organization (standard ISO 7 bit code)

ESB
Extended seven bit

EPS
Extended padded Sabre

All of the above codes indicate that incoming messages should be passed to the input message editor (UII) package. To bypass UII, either PSBN, PBTN or ISON should be entered. If the IND field is omitted, PSB is assumed. PLN or TIA may be coded or defaulted to zero if IND field specifies that UII is to be bypassed (PSBN, PBTN, ISON, ESBN or EPSN).

One table must be entered for each routing table desired. If no routing tables are required, positional parameters may be omitted.

NLRT=n
Number of slots in the SLC routing table. NLRT must be the number of routing tables coded in this macro. If room for additional routing tables is to be provided for, NLRT must be larger than the number of tables that are coded.

NLINK=n
Number of SLC links in the system. If pseudo-lines were entered in LINES (PLSNS), this parameter cannot equal zero.

N1LNK=n
Number of SLC links with 1 AI line pair. N1LNK must be less than or equal to NLINK.

NPOOL=96|n
Number of SLC input pool records for each SLC link. (Must be a multiple of 8). The fixed record type #LKIBR must be specified by the RAMFIL macro and must be a minimum of (NLINK multiplied by NPOOL).

ILCBQ=n
Number of slots in the input link control block (LCB) queue. The minimum that can be coded for this parameter is 10 × the total number of SLC lines defined in the LINES macro.

OLCBQ=10|n
Number of slots in the output LCB queue.

AILCB=36|n
The AI CXFRC/ENQ LCB-IN level (in decimal). This is the number of 128-byte blocks below which input ENQ LCBs will be discarded. The number specified must be considerably less than N128 specified in the CORREQ macro.

AILST=READY|INPUT
Defines the routing of input message blocks from CCP to OPZERO as via the INPUT or READY list.

AIRTE=INPUT|READY
Defines the routing of last or only type A input message block from CMR1 to CMR3. If the AILST parameter equals INPUT, AIRTE is not required and if coded will be ignored.

SLCEP=NO|YES
Defines whether or not SLC support for the communication controller in EP mode is desired.

Examples

This example defines two SLC routing table entries. Both lines use the padded Sabre (ALC) line control. It is assumed that the LINES macro has two SLC and two pseudo SLC lines defined. Two additional slots will be defined for the routing table. All other nondefined fields will default.

SYNCLK (01,7070,70,01,01,PSB),          X
     (02,7171,71,02,02,PSB),            X
     NLRT=4,NLINK=2,N1LNK=2,SLCEP=YES

References

None.