Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

ASSEMBLER programming interface

&pagelevel(2)&pagelevel

An FT request can also be issued from an application program.
To do this, openFT (BS2000) has an ASSEMBLER programming interface.

For file transfer with FTAM partners, please note the special points described in the openFT manual "Concepts and Functions".

Macro with EXECUTE format

Name

Operation

Operand

[name]

<macro>

MF=({E,adr / n(r)}

The symbolic address adr or the register r refers to the operand list.

The user creates such a list in one of two ways.

Macro with DSECT format

This gives you the layout of the operand list.

Name

Operation

Operand

[name]

<macro>

MF=(D[,xxx])

The prefix xxx may contain up to 3 characters and must generate names which are permissible in ASSEMBLER.

To fill the HEADER, the user must generate an initialized header pattern using the following call:

Name

Operation

Operand

[name]

<macro>

HEADER

This macro call generates a default header for the macro parameter field. This default header is to be copied into the corresponding field (e.g. xxxHADS for SHWFTADS) of the operand list using an MVC command (length 4).

The DSECT length fields must contain the exact length of the operand fields (value fields) in the program. “Fillers” such as blanks are considered to be part of the operand and will be evaluated, which will lead to syntax errors. If an operand is not evaluated, the value of the address field and the length field will be set to binary zero.

Macro with LIST format

Name

Operation

Operand

[name]

<macro>

MF=L,Operand

The operand values are addressed using the symbolic addresses adr. ASSEMBLER ́s implicit lengths of these fields must correspond exactly to the length of the value field (no fillers!). If, for example the operand PARTNER has the VALUE C’ABAB’, it cannot be entered in the form adr DC 2C’AB’, since in this case the implicit length of the fields equals 2 instead of 4.

For this format, the user need not worry about the HEADER, since it is automatically generated internally.

Macro with default format

Name

Operation

Operand

[name]

<macro>

Operand

If the MF parameter is missing for the macro for NCAN, NCOPY, NCOPYSYN and NSTAT, an operand list like the one for MF=L is generated. For all others, the address is also loaded in register 1 and the macro is executed as in MF=E. Please note that macros with default format are not reenterable.

Information on value assignments

If FTAC functionality is used, the user can define a transfer admission for FT requests which must be entered to work with an admission profile.

Please note that any transfer admission which is entered alphanumerically at the command interface must be entered in lower case letters at the programming interface.

If parameters are not explicitly specified, openFT will assign the same default values as for the commands.

Exception

For fields which identify an FTAC security level, the value 0 stands for the security level 0. In other words, it blocks that function! (fields: xxxMOSND, xxxMORCV, xxxMISND, xxxMIRCV, xxxMIPRC for the call MODFTADS and xxxMPLV for the calls CREFTPRF and MODFTPRF).

The value fields must not contain any fillers, i.e. the length fields must indicate the exact length of the value fields.

Enter keywords into the DSECT fields with the help of the above-mentioned equates.

Programs can run in 24 or 31 bit mode. Please note that addresses in 24 bit mode must have an initial 0.