This standard describes two alternative generic procedures for any program that processes sequential files organized logically into record groups. GB/T 15697-1995 Information processing Procedures for processing sequential files in record groups GB/T15697-1995 Standard download decompression password: www.bzxz.net

GB/T15697—1995
This standard is equivalent to the international standard ISO6593:1985 "Procedure flow of information processing for processing sequential documents by record group". This standard is consistent with the international standard in both technical content and format. From the date of implementation of this standard, the original electronic industry standard SJ/Z9062—87 "Procedure flow of information processing for processing sequential documents by record group" of the People's Republic of China shall be abolished.
This standard shall be implemented from April 1, 1996. Appendix A of this standard is the appendix of the standard; Appendix B is the appendix of the suggestion. This standard is proposed by the Ministry of Electronics Industry of the People's Republic of China. This standard is under the jurisdiction of the Standardization Institute of the Ministry of Electronics Industry. This standard is drafted by the Standardization Institute of the Ministry of Electronics Industry. The main drafters of this standard are Feng Hui, Huang Weimin, Wang Jiazeng, Zheng Renjie, and Duan Xiang. 573
GB/T15697.-1995
ISOForeword
The International Organization for Standardization (ISO) is a worldwide organization composed of national standardization organizations (ISO member groups). The organization prepares international standards through its technical committees. Every member group interested in a profession for which a technical committee has been established has the right to participate in the technical committee. Official or non-governmental international organizations associated with ISO can also participate in the preparation of international standards.
The draft international standard is adopted by the technical committee and circulated to the relevant member groups for voting and approval, and then accepted by the ISO Council as an international standard. The conditions for their approval are that they should meet the requirements of the ISO Constitution and at least 75% of the member groups must vote in favor. This International Standard ISO 6593 was prepared by Technical Committee ISO/TC97\Information Processing Systems. Users should note that all versions of International Standards are revised from time to time. References to any other International Standard refer to its latest version unless otherwise stated.
National Standard of the People's Republic of China
Information processing
According to record groups
Program flow for processing sequential files
Information processing-Program flow for processingsequential files in terms of record groups1 Scope and application areas
GB/T15697—1995
idt ISO 6593:1985bzxz.net
1.1 This standard describes two alternative general procedures (Method A and Method B) for use in any program that processes sequential files organized logically into groups of records.
Method A - Verify control front-end conditions after termination of the appropriate level. Method B - Verify control front-end conditions before initialization of the appropriate level. Both are based on identifying, for each record to be processed, a variable whose value affects the flow of control. 1.2 The procedures described provide a basis for designing programs that: a) process one or more input files sequentially; b) access each input file in a logical order defined by the set of records; and c) each record in the input file contains specific data items that are used to determine whether a control change is required in the processing sequence.
1.3 The processes described in this standard are subject to the following restrictions: a) Data items that determine control changes are used to form a logical sequence of layers, so that a control change at one layer implies a control change at the lower layer;
b) This standard only describes input files that are processed sequentially; c) The described processes do not specify routines that depend on user problems or installation, especially the following points: 1) Complete process initialization;
2) The order of access to more than one input file; 3) The method of assembling logical records for processing; 4) The corresponding actions taken when there is or is no control interruption at any layer; 5) Any normal processing;
6) Complete process termination.
2 Definitions
The following definitions apply to this standard.
2. 1 complete procedure complete procedure All activities described by this standard from the entry of a procedure to the exit of the procedure. 2.2 main procedure
All activities within a complete procedure from the general initialization routine to the general termination routine. 2.3 logical record logical record
Approved by the State Administration of Technical Supervision on August 30, 1995, and implemented on April 1, 1996
GB/T 15697--1995
A collection of data processed by a single-choice main procedure. Note: It may be part or all of a single physical record or part or all of a group of records. 2.4 first input routine first input routine Activities that require a logical record (if any) to be obtained and processed first. 2.5 input routine input routine Activities that require a logical record to be obtained and then processed. Note: If no logical record can be processed, the input end condition becomes true. 2.6 Control field control field
consists of one or more input variables whose values ​​may change or not change, and which affects the control flow of the main process between consecutive logical records. 2.7 level
if a logical record contains multiple control field elements, it is assumed that these elements have a hierarchical relationship with each other in order to indicate a logical grouping. The appropriate position in the hierarchy is called a level and is indicated by the level number. NOTE: In this standard, only the level numbers are assigned as follows: the lowest level control field element is level 1, followed by level 2, and so on. If there are n levels, the highest level control field element shall be at level n.
2.8 Level 1 control break level 1 control break the condition that occurs when the value of a control field element in the current logical record (and at a specified level) differs from the value of some element of the immediately previously processed logical record.
NOTE: The value of a control field element shall be obtained from the initialization routine of the appropriate level for the current logical record. When a value changes at a level above level 1, the actions of checking the control fields occur and registering control interruptions at all levels below the level at which the change actually occurred. 2.9 level 1 record group A level 1 record group is a collection of records whose control field elements refer to those of all levels 1 and above. 2.10 level 1 termination routine The activities required when a level 1 control interrupt occurs to end processing of all records belonging to a level 1 record group. 2.11 level 1 initialization routine The activities required when a level 1 control interrupt occurs to begin processing of all records belonging to a level 1 record group. 2.12 unchanged level The activities required when a level 1 control interrupt occurs but does not occur in a level 1 control interrupt. 3 Description of Method A
The description in this chapter should be read together with Figure 1, where "\n" is "3". At the beginning of the complete process, the program performs the necessary initialization actions (for example, if it has not been allocated in advance, then get and open the input file), and then the program enters the first input routine and checks whether there is actual input data to be processed. If not, the test program executes the empty file processing routine and exits the complete process through the termination routine of the complete process. If there is input data to be processed, the program executes the general initialization routine, and then enters the initialization routine of this layer in turn, starting from the highest layer until the initialization of layer 1 is completed. The program then enters the normal processing routine of the first logical record. Thereafter, the program repeats the iteration, starting from layer 1 and testing the control interrupt for each logical record. As shown in 2.As defined in clause 8, if a value does change at a layer, a control break is registered at all layers below that layer. Thus, if there is no control break at layer 1 and there is no change in value for any control field element, the program enters the unchanged layer 1 routine (when used) and continues with the normal processing routine for the current logical record. If a control break occurs at layer 1, the program enters the layer 1 termination routine and then tests for a control break at layer 2. If there is no control break at layer 2, control flow passes through unchanged layer 2 (when used), layer 1 initialization, and normal processing routines in sequence. Otherwise, the layer 2 termination routine is entered and layer 3 is tested for a control break, and so on. If there is a control break at the highest layer or at layer, the control break is registered at all layers below that layer and a layer termination action is generated for each layer including the above layers. The program then tests whether the input termination condition is true. If so, it executes the general termination routine 576
GB/T15697-1995
and exits the complete process via the termination routine of the complete process; otherwise, it enters the layer initialization routines from layer n to layer 1 in sequence before entering the normal processing routine.
4 Description of Method B
The description of this chapter should be read in conjunction with Figure 2.
At the entry of the complete process, the program performs the necessary initialization actions (for example, if it has not been previously allocated, it obtains and opens the input file), then the program enters the first input routine and checks whether there is actual input data to be processed. If not, the program exits the complete process via the termination routine of the complete process. If there is input data to be processed, the program enters the layer initialization routines in sequence, starting from the highest layer until the initialization of layer 1 is completed, and then enters the normal processing routine of the first logical record. Thereafter, the program repeats the iteration, testing the control interrupt for each logical record starting from layer 1. As defined in Section 2.8, if a value does change at a layer, a control break is registered at all layers below that layer. Thus, if there is no control break at layer 1, and there is no change in value for any control field element, then the program continues with the normal processing routine for the current logical record. If a control break occurs at layer 1, then the program enters the layer 1 termination routine and then tests for a control break at layer 2. If there is no control break at layer 2, then control flow passes sequentially through the layer 1 initialization and normal processing routines, otherwise it enters the layer 2 termination routine and tests for a layer 3 control break, and so on.
If there is a control break at the highest layer, or at layer n, then the control break is registered at all subordinate layers and a layer termination action is generated at each layer including layer n. The program then tests whether the input is complete and, if true, exits the complete process via the complete process termination routine; otherwise, it enters the layer initialization routines sequentially from layer n to layer 1 before entering the normal processing routine. If there are any requirements for unchanged layer routines, appropriate actions can be added to the initialization and/or termination routines. 577
Complete process
Initialization routine
Execution procedure
Empty file processing
GB/T15697—1995
First input
Routine library
Input data
Use initialization
Routine
Layer 2 initialization
Execution procedure
Layer 1 initialization
Routine
Normal processing
Input routine
1） If unchanged layer routines are required, insert here: Processing Control
Layer 1 Termination
Routine
Processing Control
Layer 2 Termination
Routine
Figure 1 Method A Flowchart
Processing Control
Layer n Termination
Routine
End of Input
General Termination
Routine
Complete Procedure
Routine
Complete Loading Procedure
Initialization Routine
Execution Procedure
GB/T 15697-1995
First
Routine
Layer initialization
Routine
Processing control
Layer 2 initialization
Minhang sequence
Processing control
Layer 1 initialization
Routine
Processing control
Normal processing
Input routine
Figure 2 Method B flow chart
Complete End of the process
End of the process
End of the process
End of the process
End of the process
End of the process
A1 Organization of the control field
GB/T15697--1995
Appendix A
(Appendix to the standard)
Implementation suggestions
The elements in the control field may be adjacent or non-adjacent. This arrangement of adjacency has its advantages, but the layout of the logical record should be subject to other considerations. If the arrangement shown in Figure A1 is feasible, it should be considered in the implementation. Otherwise, in order to facilitate the access of the control discontinuous test, the logic of the input routine should place the control field elements in a certain area of ​​the working memory. The control fields are arranged in order of significance, with the highest level control field element (level n) being the most significant field, followed by a number of additional control field elements and the lowest level control field element (level 1), which is the least significant field. When testing for level 1 control discontinuities, the control field elements of the current logical record are compared with previously processed logical records in ascending order from level 1 to level n.
Table A1 shows the levels of control discontinuities to be registered for a number of consecutive logical records. It is assumed that there are four levels of control. A2 General Termination
When all input has been processed, a level termination action should be performed on all levels. Input end conditions usually occur within input routines, and it is recommended that in such cases the input routines set control fields to higher values ​​unless these values ​​are obtained by high-value records appearing on the input. In many applications, it is customary to generate relevant information when the actual end of input is reached. For example: transferring checksums to output files or printing totals on analytical data. A3 Layer Termination Routine
It should be noted that although a control interrupt can be registered as a result of checking the control field elements of the current logical record, the information content of the record does not contribute to its processing in the layer termination routine. Control field element layer n
Control field element layer 2
. Control field element layer 1
Control field parts used in control field testing Layer 4
GB/T 15697—1995
Examples of control field interrupts
Control values
Control field element contents
Appendix B
(Suggestive Appendix)
Application example: Budget analysis
Control interrupt registration
(First pass)
Layers 1 and 2
Layers 1, 2, 3, 4
Layers 1, 2.3
The maintenance file contains detailed expense expenditures organized into several groups of budget centers within the administrative department's division. There may be more than one record for a budget center, and an analysis is generated showing a summary of expenses at each grouping level. For the sake of this example, logical errors such as out-of-sequence input files or invalid control fields are not discussed here. The complete process initialization routine opens an input file and a print stream. The input routine (the first input routine) obtains the next (first) record from the input file and provides control field elements with the following values:
Level 3—Administrative Department;
Level 2—Division;
Level 1—Budget Center.
The general initialization routine clears the final totals. When all input has been processed, the general termination routine prints the final totals on a new page.
Control interrupts are registered by comparing the control fields of the current input record with those of the previously processed record. Its actions are summarized in Table B1. Notice that there are no unchanged layer routines in this example. Table B1 Control Break Actions in Budget Analysis Control Break Layers (and Meaning)
1: Budget Center
2: Department
Layer Termination Routine
Print Center Totals, Add Budget Center Totals to Department Totals
Print Department Totals, Add Department Totals to Management Totals
Layer Initialization Routine
Clear Budget Center Totals, Create Control Field Elements on All Layers of Old Records | |tt||Clear the department totals. If the number of lines remaining on this page is less than 10, start a new page.
Control break layer (and meaning)
3: Department
GB/T15697—1995
Table B1 (end)
Layer termination routine
Print the department totals and add the management department totals to the final totals
The normal processing routine should add the detailed expenses to the budget center totals. Layer initialization routine
Clear the management department totals and start a new page
If there is an error message, the complete process termination routine prints the error message and closes the input file and print stream. 582
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.