107.2.1 ADD-GEZAB

107.2.1 ADD-GEZAB

This is the original format for setting a timer job. It can be changed to short dialog later.

All parameters are always displayed for the long dialog.

When setting timer jobs the user can select from the 4 following options:

Onetime timer job, single:

This is a timer job for a onetime output at an output time specified by the user.

In order to obtain correct output, the year, month, day, hour, and minute of the starting time have to be specified. The time of output is defined via parameter STAT. The contents of parameter FILEND specify the time up to which the stored call data will be output.

It should be noted that a date can be specified as end-of-file for a onetime timer job, single.

Onetime timer job, multiple:

This is a timer job which can be used to predefine up to 3 outputs.

These 3 output starting times must be placed within one month because the year, month, and minute information of the initial, output time is selected for the second or perhaps even a third output.

Thus, only the day and hours information can be selected optionally for the 2nd and 3rd starting time.
The first starting time is to be entered analogously to "onetime timer job, single".
Starting time 2 and 3 now can be defined either by only specifying the day (the hour is selected from the 1st starting time), or by specifying the hour (the day is selected from the 1st starting time).

Another option is to enter separate information for the day and hour for starting time 2 as well as for starting time 3. In this case, however, the day and hour is to be specified for all starting times because the input is rejected otherwise.

In contrast to the "onetime timer job, single", ’0’ for the end-of-file is required input for all other timer jobs. Output then occurs from the beginning of the file up to and including the respective last date at the time of output. Subsequently, the end-of-file is marked as the new beginning of a file.

Periodic timer job, single:

This is a timer job that results in file output at periodic intervals (months, days, or hours are considered intervals).

In addition to the first starting time, a time period must be entered after which the next output occurs. This period is to be specified in months (1-12), days 1-31), or hours (1-24).

Periodic timer job, multiple:

This is a timer job which can be used to define up to three different output starting times.
However, the duration of the time period is also defined.

Up to three different starting times are entered analogously to "onetime timer job, multiple".
The duration of the time period is entered analogously to "periodic timer job, single".

However, in order to prevent output overlaps, the following restrictions must be observed:

•

If the distance between the individual output times is more than one day (i.e., different days were specified for the starting times), then the shortest possible time period that can be specified is 1 month; days and hours are not possible. (If such an entry is made, an error message is received.)

•

Is the difference between the individual output times only in hours (the same day was selected for the output), the shortest possible time period is one day. (If hours are entered for this time period, an error message is received again.)

The following branches are possible:

•

Creation of a short dialog.

•

Creation of a long dialog.

After the successful ADD-GEZAB action, the job for the call charge data request is stored in a dialog field.
There are 8 dialog fields (parameter DIAFNO), therefore, a maximum of 8 different jobs can be created for call charge data requests.

Mandatory output / Write around:

With parameters
DEV=NODEV, DEL=Y, FOUT=Y
the GEZ data records are "written around", this means that the oldest 20% of GEZ data records are deleted automatically.

When starting the action ADD-GEZAB with mode "S" (short dialog) all parameters are changed, except the two parameters CALLUP and PERIOD.

Procedure Overview


Command Code	Parameter
ADD-GEZAB	TYPE=S,DIAFNO=<number>,[FILE=<character>]	(1)
	,[FILESTA=<string>],[FILEND=<string>],[DEV=<string>]
	,[DEL=<Y/N>],[FORM=<string>],[BLKSIZE=<number>]
	,[FOUT=<Y/N>],STAT=<string>
	,[MULTOUT=N],[SELSTOP=<Y/N>];
	\|[MULTOUT=Y],{(min 1)STADAY2=<string>,STADAY3=<string>
	,STAHR2=<string>,STAHR3=<string>},[SELSTOP=<Y/N>];

	\|TYPE=L,DIAFNO=<number>,FILE=<character>
	,FILESTA=<string>,FILEND=<string>

	,DEV=DP,CALLUP=<Y/N>,DEL=<Y/N>
	,FORM=<string>,BLKSIZE=<number>
	,FOUT=<Y/N>,STAT=<string>
	,MULTOUT=N,PERIOD=<string>,SELSTOP=<Y/N>;	(2)

	\|MULTOUT=Y,{(min 1)STADAY2=<string>,STADAY3=<string>	(3)
	,STAHR2=<string>,STAHR3=<string>}
	,PERIOD=<string>,SELSTOP=<Y/N>;

	\|DEV=NODEV,DEL=<Y/N>,FOUT=<Y/N>;	(4)

	\|DEV=<DEV1/DEV2/DEV3/DEV4/TAPE/FT>,DEL=<Y/N>
	,FORM=<string>,BLKSIZE=<number>,FOUT=<Y/N>
	,STAT=<string>
	,MULTOUT=N,PERIOD=<string>,SELSTOP=<Y/N>;	(5)

	\|MULTOUT=Y,{(min 1)STADAY2=<string>,STADAY3=<string>	(6)
	,STAHR2=<string>,STAHR3=<string>}
	,PERIOD=<string>,SELSTOP=<Y/N>;

1.

The customer request is as follows:

Monthly evaluation,
Output of data from 12. April 2000, 00:00 a.m. to 19. April 11:59 p.m.
Time of output: 7. September 2000, 10:00 a.m.
The immediate output is to be blocked during output.
Subsequently, the data are to be deleted.

ADD-GEZAB:TYPE=L,DIAFNO=1,FILE=CDRC1,FILESTA=0004120000,FILEND=0004192359,DEV=DEV1
,DEL=Y,FORMAT=FORM01,BLKSIZE=50,FOUT=Y,STAT=0009071000,MULTOUT=N,PERIOD=0
,SELSTOP=Y;

2.

Same as example 1, except output is to occur at the 1st of each month.

ADD-GEZAB:TYPE=L,DIAFNO=2,FILE=CDRC1,FILESTA=0004120000,FILEND=0,DEV=DEV1,DEL=Y
,FORMAT=FORM01,BLKSIZE=50,FOUT=Y,STAT=0010011000,MULTOUT=N,PERIOD=01M
,SELSTOP=Y;

3.

Output is to occur at the 1st and 15th of each month

ADD-GEZAB:TYPE=L,DIAFNO=3,FILE=CDRC1,FILESTA=0004120000,FILEND=0,DEV=DEV1,DEL=Y
,FORMAT=FORM01,BLKSIZE=50,FOUT=Y,STAT=0010011000,MULTOUT=Y,STADAY2=15
,STAHR2=08,PERIOD=01M,SELSTOP=Y;

If a timer job has been activated for a dialog field, the dialog field can be rewritten only if the current timer job is stopped (STOP-GEZAB). In that way the state of the dialog field changes from TIMED ORDER RUNNING to state BUSY.

1.

Preparation: Creation of dialog field 1 with long dialog.

ADD-GEZAB:TYPE=L,DIAFNO=1,FILE=CDRC1,FILESTA=0,FILEND=0,DEV=DEV1,DEL=Y
,FORMAT=FORM01,BLKSIZE=1,FOUT=Y,STAT=0,MULTOUT=Y,STADAY2=30,STAHR2=12
,PERIOD=01M,SELSTOP=Y;

2.

Stopping of state TIMED ORDER RUNNING for dialog field 1.

STOP-GEZAB:DIAFNO=1;

3.

Modifying some values in the dialog field 1 with short dialog.

ADD-GEZAB:TYPE=S,DIAFNO=1,FILESTA=0004121200,STAT=0,MULTOUT=N;

${DocTitle}, ID: ${DocID}

© 02/2025 Mitel Networks Corporation. - All rights reserved.
Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG.
All other trademarks herein are the property of their respective owners.