Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Basic structure of an SDF start procedure

The following example shows an SDF start procedure. As recommended when using SDF-P, BEGIN-BLOCK, END-BLOCK, and IF-BLOCK-ERROR are used.

/SET-PROCEDURE-OPTIONS                                 -
/        CALLER               = ANY                    -
/       ,IMPLICIT-DECLARATION = YES                    -
/       ,LOGGING              = YES                    -
/       ,INTERRUPT-ALLOWED    = YES                    -
/       ,INPUT-FORMAT         = FREE                   -
/       ,DATA-ESC             = STD                    -
/       ,SYS-FILE             = STD                    -
/       ,DATA-ERROR           = YES                    -
/       ,JV-REPLACEMENT       = AFTER-BUILTIN-FUNCTION
/BEGIN-PARAMETER-DECLARATION
/&* -------------------------------------------------
/&* here you can declare your Procedure-Parameters
/&* -------------------------------------------------
/END-PARAMETER-DECLARATION
/&* -------------------------------------
/&* here is place for your variables
/&* -------------------------------------
/ SET-FILE-LINK LINK-NAME=SYSLOG,FILE-NAME=<applname>.SYSLOG
/ MODIFY-TEST-OPTION DUMP=YES
/ ASSIGN-SYSDTA TO-FILE=*SYSCMD
/ ASSIGN-SYSOUT TO-FILE=SYSOUT.&(TSN()).<applname>
/&* ----------------------------------------------------------------
/&*  Here follows the section with the SET-FILE-LINK commands if
/&*   at least one LOAD-MODULE is defined with
/&*   ALTERNATE-LIBRARIES = YES.
/&*  If you need RFA connections, or an AID connection (AID-FE)
/&*   for testing an UTM production application or other
/&*   connections please insert here the commands.
/&* ----------------------------------------------------------------
/REPEAT: BEGIN-BLOCK
/ SHOW-FILE-LINK LINK-NAME=KDCDUMP
/&* ----------------------------------------------------------------
/&*  If you want to do some actions after PEND ER, then you must
/&*   insert commands here. (E.g. prepare an UTM dump.)
/&* ----------------------------------------------------------------
/ REMOVE-FILE-LINK LINK-NAME=KDCDUMP
/ GOTO EXEC
/ IF-BLOCK-ERR; END-IF
/&* --------------------------------------------------
/&* here is place for actions after KDCAPPL PROG=NEW
/&* --------------------------------------------------
/EXEC:
/ MOD-DBL-DEFAULTS SCOPE=*CMD-CALLS(               -
/      LOAD=*PAR(LOAD-INF=*REF),                   -
/      RESOLUTION=*PAR(SHARE-SCOPE=*NONE),         -
/      ERROR-PROC=*PAR(UNRESOLVED-EXTRNS=*DELAY),  -
/      REPORT=*PAR(MES-CONTR=*WARN,                -
/                  PROG-MAP=*SYSLST) )
/ START-EXEC-PROG FROM-FILE=*LIBRARY-ELEMENT (     -
/                    LIBRARY  = <libname>          -
/                    , ELEMENT  = <elem>)
.UTM START FILEBASE  = <applname>
.UTM START ROOTNAME  = <rootname>
.UTM START TABLIB    = <root-lib>
/&* ----------------------------------------------------
/&* in this section you can insert the parameter(s)
/&* for node-recovery  for example:
/&* .UTM START NODE-TO-RECOVER=<nodename>,RESET-PTC=Y/N
/&* ----------------------------------------------------
.UTM START ENTER-PROC-INPUT='STRT-ENTER-PROC'
/&* ----------------------------------------------------
/&* if your enter-procedure has parameters you have to
/&* change the last line with correct syntax
/&* if necessary duplicate the parameter-line
/&* ----------------------------------------------------
.UTM START TASKS     = 3
.UTM START TASKS-IN-PGWT     = 0
.UTM START ASYNTASKS = 2
.UTM START TESTMODE  = OFF
.UTM START STXIT     = ON
.UTM START BTRACE    = OFF
.UTM START OTRACE    = OFF
.UTM START DB-CONNECT-TIME = 0
.UTM END
/&* ----------------------------------------------------------------
/&*  Here follows the section with the data base and format system
/&*   parameters (if necessary).
/&* ----------------------------------------------------------------
.FHS MAPLIB          = <maplib>
END
/ GOTO REPEAT
/ IF-BLOCK-ERR
/ SHOW-FILE-LINK LINK-NAME=KDCTRMAP
/&* -----------------------------------------------------------
/&*  If you want to do some actions after abnormal application
/&*   termination, then you can put some commands here.
/&* -----------------------------------------------------------
/ END-IF
/ END-BLOCK REPEAT
 / GOTO EXIT
/ IF-BLOCK-ERR; END-IF
/&* --------------------------------------------------------
/&*  Here you can insert commands to execute after normal
/&*   application termination.
/&* --------------------------------------------------------
/EXIT:
/ REMARK
/EXIT-PROC