Previous Topic Next topic Print topic


Resolving Original Scheduling (%%O and %%$O) System Date Variables

The Control-M AutoEdit facility can define or export these OS environment variables before executing MFBSIJCL or the script that executes MFBSIJCL.

PARMS ODATE=%%ODATE [CENT=%%CENT] may also be used in the MFBSIJCL command line to set %%ODATE and %%CENT.

When MFBSIJCL starts execution, it retrieves ODATE and CENT OS environment variable values. These are saved in the MFBSI symbols pool to resolve %%ODATE, %%ODAY, %%OMONTH and %%OYEAR found in the JCL member to be executed. Based on the values of these variables, additional Control-M AutoEdit variables are evaluated and stored in MFBSI symbols pool:

When MFBSI is used with a scheduler other than Control-M, the OS variables ODATE, ODAY, OMONTH, OYEAR and CENT must be explicitly defined whenever %%ODATE, %%ODAY, %%OMONTH, %%OYEAR, %%$DATE, %%$OYEAR, %%OJULDAY, %%$OJULDAY, %%OWEEK, %%OWDAT or %%$CENT require resolution in the JCL. Control-M resolves these system variables based on the current OS system date.

If CENT is not defined in the OS environment, the current OS system century is used.

Example

This example shows a Control-M set/export ODATE=010201 (1 Feb.) and CENT=20 (year 2001) and variables defined in the MFBSI symbols pool at MFBSIJCL initialization.

9 //* %%LISTVAR
10 //*
--------------------------------------------------------------------<LISTVAR
11 //* ODATE = [010201] <LISTVAR
12 //* OYEAR = [01] <LISTVAR
13 //* OMONTH = [02] <LISTVAR
14 //* ODAY = [01] <LISTVAR
15 //* $ODATE = [20010201] <LISTVAR
16 //* $OYEAR = [2001] <LISTVAR 
17 //* OWEEK = [05] <LISTVAR
18 //* OWDAY = [4] (if first day of week is defined as Monday) <LISTVAR
19 //* OJULDAY = [032] <LISTVAR 
20 //* $OJULDAY = [2001032] <LISTVAR 
21 //* $OCENT = [20] <LISTVAR 
22 //*
--------------------------------------------------------------------<LISTVAR
Previous Topic Next topic Print topic