Create revision packet
This function can be used to create product-specific correction packets (supply components). These serve as the input for the depot of the next user group. Each supply component (SC) is identified with a version number (SC-Vers) which is automatically allocated in user groups 1, 2 and 3 and entered in the depot as the delivered packet.
In user group 4 (customer ́s internal computer center), only the delivery packets added to the depot can be recreated as a file.
Creation of current delivery packet
This function can only be used by user groups 1, 2 and 3.
To deliver current packets, i.e. supply components taking due account of the notebook, the corresponding supply component version must be input or marked in the selection screen.
When creating a delivery packet from user group 1, the loader letter suggested by RMS can be changed in the confirmation screen. In the following screen, the user can choose between a complete delivery of all text entries or a packet showing only the differences for a specific supply component version.
Before the delivery is carried out, a check is performed to determine if a description exists in the text level SC-OPT DESCRIPTION for all optional corrections. If a description is missing, then the SUBNO of the missing texts is listed in the log file.
If texts are missing, the delivery is terminated and the SUBNO of the missing texts is listed in the log file.
For the rest of the corrections, all text levels are searched and the first entry is written in the output file.
Each delivery can be checked. The field Check Delivery must be selected for this. All details of the desired delivery are checked.
Output file name:
The output file name can be defined in the statement line. Otherwise the following default file name is generated:
SYSRMS.<product>.<version>.<sc-version>
Create original delivery packet
This function is available to all 4 user groups. Each user can carry out this operation, since no entries and modifications are carried out in the depot.
To create original packets, i.e. accepted or already delivered packets, the field Original delivery must be selected.
Supply component version number
A version number has the following form: B01.03
The first three characters are assigned automatically by the central service, the last two by the regional service.
The loader letter (first character) has only been retained for historical reasons. It determines the order in which the delivery packets are created by the central service. (B00.00 before C00.00 etc.).
The numerical values are only raised in a current delivery if modifications (notebook entries) were made to the previous version in the respective depot.
In the case of a customer-internal delivery, the loader letter is changed from uppercase to lowercase (e.g. B ==> b).
Input revision packet into depot
This function is used to integrate supply components (REP packets, text packets and software configurations) which were created in the previous user group’s depot into the user group’s depot.
Every current supply component to be accepted contains all of the delivery depot’s corrections which are valid at the time of creation
The following input logic applies:
CORRECTIONS (REP)A correction is only physically saved in the depot once for each product. For future acceptance procedures, only a logical assignment is created.
TEXTSEvery text is accepted, i.e. texts already existing in the depot are overwritten if they have the same text level name and text key.
SW-KONFEvery product group is compared with the groups already saved in the depot and if they are not already in the depot, then the software configuration is extended to include these product groups. The attributes are always saved, but are only used actively if no modifications of the software configuration attributes are made in the depot.
A delivery packet can consist of several supply components (SC), text levels (TL) and software configurations (SW-C). An input packet can consist of several delivery packets.
The product-specific software configuration is a fixed component of the delivery file. Whenever a new delivery is added, the configurations found in the depot are automatically brought up to date.
Every supply component and text level is identified using its own control line. These are automatically generated during a delivery. The control lines must not be modified.
The control lines for a text level (TL) can be created by any user to set up his own TLs. 32767 text levels are available. On input of a packet, the contents of existing TLs can be modified. The creation and modification of text levels can also be performed using the text editor.
The format of the inputs for text levels has the following form:
Control line format
KKKTTTTTTTTTTTTTTTTTTTTTT*********dd/mm/yy***********************************
Explanation:
KKK | Text level identifier |
| Text level name (22 characters) |
| Date |
Example:
*T*SC-REP DESCRIPTION *********<date>***********************************
Text line format
PPPPPPPPBBBBBtexttext...
Explanation:
| PM (8 characters) |
| 5 blanks or, if applicable, -xxx- whereby xxx is the jd |
| PATCH-DESCRIPTION from PULS |
Example:
*T*SC-REP DESCRIPTION *********<date>*********************************** A0326168 FUNCTION NAME: Name of the OPT correction A0346168 Here comes the PATCH-DESCRIPTION from PULS!
The input packets can be assigned using the link name “EINDAT”, otherwise a prompt will come up in interactive mode asking for the file name.
For every product which is added to the depot, a comparison list is created in the log file.
Output file (edited for printing): INPUT.LIST.hhmmss
This log contains an overview of the differences for the last input packet of the product and the notebook cross-match. If the new packet is identical, interactive users can decide whether to accept it or reject it.