Some standard content:
1.1 Function
National Standard of the People's Republic of China
Programming language COBOL
Communication module
GB/T 4092. 13—92
Replaces GB 4092. 13-- 83
The communication module provides the functions of accessing, processing and creating messages or parts of messages. It provides the ability to communicate with the message control system (MCS) of the communication equipment.
1.2 Level characteristics
Level 1 communication provides partial functions for communication description clauses. In the procedure section, level 1 communication provides partial functions for RECEIVE and SEND statements and complete functions for ACCEPTMESSAGECOUNT statements. Level 2 communication provides complete functions for communication description clauses. In the procedure section, level 2 communication provides complete functionality for ACCEPTMESSAGECOUNT, DISABLE ENABLE, PURGE, RECEIVE, and SEND statements. 2 Data Section of the Communication Module
2.1 Communication Section
The communication section is located in the data section of the source program. The communication section describes the data items in the source program that serve as the interface between the message control system (MCS) and the program. This MCS interface area is defined by the communication description section. The communication description section is followed by zero, one, or more record description sections. The general format of the communication section is given below:
COMMUNICATION SECTION
[Communication Description Section
［Record Description Section}}
2.1.1 Communication Description Section
In a COBOL program, the communication description section (CD section) represents the highest level of organization in the communication section. The communication section header is followed by the communication description section, which consists of a level indicator (CD), a cd name, and a series of independent clauses. The description section itself is terminated by a number. For input communication description items, these clauses specify the input queue, subqueue, message date and time, symbol source, text length, status and terminal keys, and message count. For output communication description items, these clauses specify the port address count, text length, status key, error key, and address of the symbol date. For input and output communication description items, these clauses specify the message date and time, symbol terminal, text length, status, and terminal keys. 2.1.2 Record Description Structure
The record header associated with a communication description item can be overridden implicitly by the user specifying various record description items written immediately after the communication description item.
A record description item consists of a group of data description items that describe the characteristics of a particular record. Each data description item consists of a level number followed by a data name or a FILLER clause (if specified), followed by a string of independent clauses as needed. Record descriptions can have a hierarchical structure, so the syntax for using a particular item can be quite different, depending on whether it is followed by subordinate items. The structure of the record description and the elements allowed in the record description clause are solid. Approved by the State Administration of Technical Supervision on August 4, 1992 and implemented on May 1, 1993.
GB/T 4092-13-92
It is explained in the concept of layer and data description clause. The availability of specific clauses in the data description clause depends on the level of the core module supported by the implementation. 2.2 Communication description clause
2.2.1 Function
The communication description clause specifies the interface area between the message control system (MCS) and the COBOL program. 2.2.2 General format
Format 1:
CDed name!
[[[SYMBOLICQUEUEIS data name 1]
[SYMBOLIC SUB-QUEUE-1 IS data name 2][SYMBOLICSUB-QUEUE-2IS data name 3][SYMBOLIC SUL-QUEUE-3 IS data name 4［MESSAGEDATEIS data name 5]
[MESSAGETIMEIS data name 6]
FOREINITIALINPUT
Format 2:
[SYMBOLICSOURCEIS data name 7]
[TEXTLENGTHIS data name 8]
[END.KEY IS dataname9]
[STATUSKEYIS dataname1D]
LMESSAGECOUNTIS dataname11J
[dataname1.dataname2,dataname3,dataname4,dataname5,dataname6,dataname7,dataname8,dataname9,dataname10,dataname11
cd name1 FOR OUTPUT
[DESTINATIONCOUNTIS dataname1]
[TEXT L.ENGTH IS dataname2]
[STATUSKEYIS dataname3]
『DESTINATIONTABLEOCCURS integer1TIMES[INDEXEDBY(bitmarkername1}.
[ERRORKEYIS dataname4]
[SYMBOLICDESTINATIONIS dataname5]Format 3:
CD cd Name 1www.bzxz.net
T[MESSAGEDATEIS data name 1]
[MESSAGETIMEIS data name 2]
[SYMBOLICTERMINALIS data name 3]FOR INITIALJI-0
[TEXT LENGTH IS data name 4]
［ENDKFYIS data name S]
[STATUSKEYJS. data name 6]
[data name 1, data name 2, data name 3,
data name 4, data name 5, data name 6]
2.2.3·Syntax rules
All formats!
GB/T 4092. 13--92
(1) A CD clause must and can only appear in a communication section. Formats 1 and 3:
(2) In a single program, the INITIAL clause can only be specified in one CD description clause. The INITIAI. clause cannot be used in a program that has a USING phrase at the beginning of the procedure.
(3) These optional clauses, except the INITIAL clause, can be written in any order. (4) If there are no optional clauses in the specified interface area, then the 01-level data description clause must follow the CD description clause. Any optional clause can follow the U1-level data description clause.
Format 1:
(5) The record description clause following the input CD description clause implicitly redefines the record area established by the input CD description clause and must be described as a record of exactly 87 standard data format characters. This record allows multiple redefinitions but only the first redefinition can contain a VALUE clause. However, the MCS always refers to this record according to the data description defined in General Rule 2 (see 5.15 VALUE clause in GB/T 4092.2).
(6) Data name 1, data name 2, and data name 11 must be unique in this sequence in the CD description. Any data name can be replaced by the reserved word FIL.LER.
Format 2:
(7) The order in which the optional clauses are written is irrelevant. (8) If no optional clauses are specified in the CD description, the data description clause with level number 01 must follow the CD description clause. (9) The record description clause that is subordinate to the output CD description clause implicitly redefines the record area established by the output CD description clause. Multiple redefinitions of this record are allowed, but only the first redefinition can contain a VALUE clause. However, the MCS always refers to this record according to the data description defined in General Rule 16 (see Core Module 5.15VALUE clause). (10) Dataname1, dataname2, and dataname5 must be unique in the CD description clause. (11) If the DESTINATIONTABLE(OCCRS clause) is not specified, an incorrect key and symbol area will be assumed. In this case, subscripts are not allowed when referencing these data items. (12) If the DESTINATIONTABLE(OCCRS clause) is specified, dataname4 and dataname5 can only be referenced with subscripts.
(13) At level 1, the value of the data item referenced by dataname1 must be 1. At level 2, there are no restrictions on the value of the data item referenced by dataname1. Format 3:
(14) The record description clause of the input-output CD description clause implicitly redefines the record area created by the input-output CD description clause and must describe a record of exactly 33 standard data format characters. This record can be redefined multiple times: but only the first redefinition can contain a VALUE clause. The MCS always refers to this record as defined in the data description in General Rule 24 (see 5.15 VALUE clause in GB/T 4092.2).
(15) Dataname 1, dataname 2, *, dataname 6 must be unique within the CD description. Any dataname in this sequence may be replaced by the reserved word FILLER.
2.2.4 General Rules
Format 1:
(1) The information entered into the CD description constitutes the communication between the Message Control System (MCS) and the message processing program. This information may not come from the terminal as part of a message. (2) For each input CI) description, a record field of 87 contiguous character positions is allocated. This record domain is defined as follows:
GB/T 4092. 13--92
The SYMBOLICQUFUE clause defines data name 1 as a character-type primary data item that occupies the 1st to 12th positions in the record.
bSYMBOL.ICSUB-QUEUE-1 clause defines data name 2 as a character-type primary data item that occupies the 13th to 24th positions in the record.
The SYMBOLISSUB-QUEUE-2 clause defines data name 3 as a character-type primary data item that occupies the 25th to 36th positions in the record.
d. The SYMBOLICSUB-QUEUE-3 clause defines data name 4 as a 12-character character-type primary data item occupying positions 37-48 of the record. The
MESSAGEDATE clause defines data name 5 as the name of a data item: its implicit description is an unsigned 6-digit integer occupying positions 49-54 of the record. f. The MESSAGETIMF clause defines data name 6 as the name of a data item, its implicit description is an unsigned 8-digit integer occupying positions 55-62 of the record. g. The SYMBOLIC SOURCE clause defines data name 7 as the name of a 12-character character-type primary data item occupying positions 63-74 of the record.
h. The TEXTLENGTH clause defines data name 8 as the name of an elementary data item, implicitly described as an unsigned 4-digit integer that includes the 75th to 78th positions in the record. i. The ENDKEY clause defines data name 9 as the name of a one-character symbol-type elementary data item that occupies the 79th position in the record.
The STATUSKEY clause defines data name 10 as the name of a two-character character-type elementary data item that occupies the 80th to 81st positions in the record.
i. The MESSAGECOUNT clause defines data name 1I as the name of an elementary data item, implicitly described as an unsigned 6-digit integer that occupies the 82nd to 87th character positions in the record. The second option can replace the corresponding data names defined by these clauses with a string of data names. Any option produces a record whose implicit summary is equivalent to: Implicit Description
dataname0.
dataname1
dataname2
dataname3
dataname4
dataname5
dataname6
dataname7
dataname8
dataname9
dataname10
PICTUREX(12).
PICTURE
PICTURE
PICTURE
PICTURE
PICTURE 9( 8)
PICTURE X(12).
PICTURE 9( 4).
PICTURE X.
PICTURE XX.
Symbol Queue
Symbol Subqueue 1
Symbol Subqueue 2
Symbol Subqueue 3
Message Date
Message Time
Symbol Source
Text Length
Terminal Key
Status Key
Data Name 11
CB/T 4092-13—92
PTCTURE9(6).
Note that the information under “Notes” is for clarification only and is not part of the data description. Message Count
(3) The contents of the data items referenced by Data Name 2, Data Name 3 and Data Name 4 must contain spaces when not used. (4) The data items referenced by Data Name 1, Data Name 2, Data Name 3 and Data Name 4 contain symbolic names from the column subqueue, ..., etc., respectively. All symbolic names must comply with the system name formation rules and must be predefined for the MCS. (5) A RECEIVE statement causes the serial return of the next message or part of a message from the queue specified in the CD description. During the execution of a RECEIVE statement, the input CD must contain, in the contents of dataname1, the name of the symbolic queue. The contents of the data items specified by dataname2, dataname3, and dataname4 may contain symbolic subqueue names or spaces. When a given level of the queue structure is specified, all higher levels of the queue structure must also be specified. If there is a level number less than that of all queue levels, then the MCS determines the next message or part of a message to be accessed in the queue and/or subqueue specified in the input CD. After the execution of a RECEIVE statement, the contents of the data items referenced by dataname1 through dataname4 will contain the symbolic names of all levels of the queue structure.
(6) Whenever the MCS schedules a program to process a message, that program creates an execution unit and places the symbolic name of the queue structure with this action as applicable in the data items referenced by dataname1 through dataname4 in the CD description associated with the INITIAL clause. In all other cases, the data items referenced by dataname1 through dataname4 in the CD description clause associated with the INITIAL statement are initialized to spaces. The insertion or initialization of symbol names to spaces is completed before the execution of the first statement in the procedure. The next RECEIVE statement with the same contents of the data items referenced by the specified dataname1 through dataname4 returns the actual message that caused the program to be scheduled, only then modifying the rest of the CD description clause. (7) If the MCS prompts the scheduler to schedule a program that lacks the INITIAI statement, the results will be undefined. (8) During the execution of a RECEIVE statement, in the data item referenced by data name 5, the MCS provides the date when it considers the message to be complete, in the format of 'YYMMDD' (year, hour, day). The content of the data item referenced by data name 5 can only be modified by the MCS as part of the execution of a RECEIVE statement.
(9) During the execution of a RECEIVE statement. In the data item referenced by data name 6, the MCS provides the time when it considers the message to be complete, in the format of 'HHMMSSTT (hours, minutes, seconds, hundredths of a second). The content of the data item referenced by data name 6 can only be modified by the MCS as part of the execution of a RECEIVE statement. (10) During the execution of a RECEIVE statement. In the data item referenced by data name 7, the MCS provides the symbolic name of the communication terminal that transmitted the message. This symbolic name must follow the system name formation rules. However,If the MCS does not know the symbolic name of the communication terminal: then the data item referenced by data name 7 will contain spaces. (11) The MSC indicates the number of filled character positions obtained by executing the RECEIVE statement by means of the content of the data item referenced by data name 8.
(12) The content of the data item referenced by data name 9 can only be set by the MCS as a partial result of executing a RECEIVE statement, and the setting is carried out according to the following rules:
a. When the RFCEIVEMESSAGE phrase is specified. Then: 1) If the end of the message is detected, then the content of the data item referenced by data name 9 is set to 3. 2) If the end of the message is detected, then the content of the data item referenced by data name 9 is set to 2. 3) If less than a message is transmitted, then the content of the data item referenced by data name 9 is set to 0. b. When the RECEIVESEGMEVT phrase is specified, then: 1) If the end of the message is detected, then the content of the data item referenced by data name 9 is set to 3. 2) If the end of the message is detected, then the content of the data item referenced by data name 9 is set to 2. 3) If the end of the message segment is detected, then the content of the data item referenced by data name 9 is set to 1. 4) If less than one message segment is transmitted, then the content of the data item referenced by data name 9 is 0. GE/F4092.13—92
: When more than one of the above conditions is satisfied, the content of the data item referenced by data name 9 is determined by the first condition satisfied in the list order.
(I3) The content of the data item referenced by data name TO indicates the status condition of a previously executed RECEIVE, ACCEPTMEESAGECOUNT, ENARI.FINPUT, or DISABLBINPUT statement. The actual connection between the content of the data item referenced by data name 10 and the status condition itself is defined in Figure 1 (Communication Status Key Conditions) below.
(14) The content of the data item referenced by data name 11 indicates the number of messages stored in queues 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 8 The contents of the referenced data item can only be modified as part of the execution of the ACCEPTMESSAGE(OUNT) statement.
Format 2:
(15) The essence of the output CI) description information is not sent to the terminal, it constitutes the communication between the program and the MCS related to message processing.
(16) In level 1, a record field of 23 adjacent character positions is allocated for each output (D). In level 21, for each output (D description, a record field of 23 adjacent character positions is allocated according to the following formula: (10+13*integer 1).
The implicit description of this record field is:
The FESTINATIONCOUNT clause defines data name 1 as the name of a data item, which implicitly describes the number of characters occupying the record. The
b.TEXTI.FN(HH) clause defines data name 2 as the name of an elementary data item. It is implicitly described as an unsigned 4-digit integer occupying the 5th to 8th character positions in the record. Item.
C.STATLISKEY clause defines data name 3 as a 2-character character-type elementary data item occupying the 9th to 10th character positions of the record: The character positions from 11th to 23rd and each subsequent group of 13 characters form the table items described as follows: 1) ERRORKEY defines data name 4 as a 1-character character-type elementary data item name. 2) SYMHOI.ICSTINATION clause defines data name 5 as a 12-character character-type data item name: Use the above clauses to generate A record whose implicit description is equivalent to: Implicit Description
Data Name 0
Data Name 1
Data Name 2
Data Name 3
Data Name
Data Name 4
Data Name 5
PICTURE
PICTURE
PICTURE
INTEGER 1TIMES
FICTURE
PICTURE
Count of H
Body Length
Status Key
Destination Table
Error Key
Symbol Destination
Note: The information listed under "Notes" is for clarification and is not part of the data summary. (17) During the execution of a SENDPURGE, ENABIEQUTPUT, or DISABLEOUTPUT statement, the contents of the data item referenced by data name 1 are used by MCS to identify symbolic destinations that use the area referenced by data name 5. MCS finds the first symbolic destination name in the 1st occurrence of the area referenced by data name 5, the second symbolic destination name in the 2nd occurrence of the area referenced by data name 5, and so on, until the area referenced by data name 5 is identified by the contents of data name 1. During the execution of a SENDPURGE, ENABIEQUTPUT, or DISABLEOUTPUT statement, if the value of the data item referenced by data name 1 is outside the integer range 1, an error condition is generated, no action is taken for any destination, and execution of the SEND, PURGE, ENABLEOUTPUT, or DISABLEOUTPUT statement is terminated. (18) It is the user's responsibility to ensure that the value of the data item referenced by data name 1 is valid at the time of the execution of a SENDPURGE, ENABLEOUTPUT, or DISABL.FUTIUT statement. (19) As part of the execution of a SEND statement, the MCS interprets the contents of the data item referenced by data name 2 as an indication of the number of left-most character positions of the data item referenced by the identifier in the corresponding SEND statement that transmitted the data (see 3.6 SEND statement).
(20) Each occurrence of the data item referenced by data name 5 contains the name of a previously known destination. These names must obey the system name formation rules. (21) The content of the data item referenced by data name 3 indicates the status condition of a previously executed SENDPURGE, ENABLEOUTPUT, or DISABL.FUTIUT statement. The actual relationship between the contents of the data item referenced by data name 3 and the status condition itself is defined in Table 1 (Communication Status Key Conditions) below.
(22) During the execution of a SEND, PURGE, ENABLEOUTPUT, or DISABLEOCTPUT statement, if the MCS determines that there is an error, the contents of the data item referenced by dataname3 and the contents of each occurrence of dataname4, up to and including the occurrence indicated by the contents of dataname1, are modified.
The actual relationship between the contents of the data item referenced by dataname4 and the error condition itself is defined in Table 2 (Error Key Values) below.
Format 3:
(23) The information in the input/output CD description item constitutes the communication between the MCS and the program regarding the processing of the message. This information shall not arrive from the terminal as part of the message.
(24) For each input/output CD description item, a record field of 33 contiguous character positions is allocated. This record field is defined for the MCS as follows:
a, The MESSAGE DATE clause defines dataname1 as the name of a data item. Its implicit description is the unsigned 6-digit integer in character positions 1 to 6 of the record. b. The MESSAGETIME clause defines dataname 2 as the name of a data item. Its implicit description is an unsigned 8-digit integer occupying character positions 7 to 14 of the record.
d. The TEXT LENCTH clause defines dataname 4 as the name of an elementary data item. Its implicit description is an unsigned 4-digit integer occupying character positions 27 to 30 of the record.
e. The ENDKEY clause defines dataname 5 as the name of a one-character elementary data item occupying character position 31 of the record. f. The STATUSKEY clause defines dataname 6 as the name of a two-character elementary data item occupying character positions 32 and 33 of the record.
e. Optionally, a data name may be substituted for the corresponding data name defined by these clauses. The optional ... records are generated, whose implicit description is equivalent to the implicit description
01dataname.
02dataname1
PICTURE9(6).
Message opening period
02Data name 2
02Data name 3
02Data name 4
02Data name 5
02Data name 6
PICTURE9(8).
GB/T 4092.13—92
PICTUREX(12)
PICTURE 9(4).
PICTURE X.
PICTURE XX.
Message time
Symbol terminal
Text length
Tail key
Status key
Note that the information under "Notes" is for clarification and is not part of the data description. : (25) When the MCS schedules a program to process a message, the first RECEIVE statement that references the input/output CD with the INITAL clause returns the actual message that caused the program to be scheduled. (26) Data name 1 has the format 'YYMMDD (year, month, day). Its contents represent the date when the MCS considers the message complete. The contents of the data item referenced by data name 1 are modified only by the MCS as part of the execution of a RECEIVE statement. (27) Data name 2 has the format 'HHMMSSTT' (hours, minutes, seconds, hundredths of a second). Its contents represent the time when the MCS considers the message complete.
The contents of the data item referenced by data name 2 are modified only by the MCS as part of the execution of a RECEIVE statement. (28) Whenever the MCS schedules a program to process a message, that program establishes an execution unit and the symbolic name of the communication terminal that is the source of the message called by that program is placed as applicable in the data item referenced by data name 3 in the input/output CD description associated with the INITIAL clause. This symbolic name must follow the system name formation rules. In all other cases, the contents of the data item referenced by dataname3 in the description of the input-output CD associated with the INITIAL clause are initialized to spaces.
Symbol name insertion or initialization to spaces is performed before the first statement in the procedure is executed. (29) If the MCS prompts to schedule a program that lacks an INITIAL clause, the results will be undefined. (30) When an INITIAL clause is specified for an input-output CD and the MCS schedules the program, the contents of the data item referenced by dataname3 cannot be changed by the program. If the contents are changed, execution of any statement referencing cdname1 is unsuccessful, and when applicable, the data item referenced by dataname6 is indicated as an unknown source or destination (see Table 1 for communication status key conditions). (31) For an input-output CD without an INITIAI clause, or for an input-output CD with an INITLAL clause, when the program is not scheduled by the MCS, the program must specify the symbolic name of the source or destination in dataname3 before the first statement referencing cdname1 is executed.
After the first statement referencing dataname1 is executed, the contents of the data item referenced by dataname3 cannot be changed by the program. If the contents are changed, execution of any statement referencing dataname1 is unsuccessful, and the data item referenced by dataname6 is marked as an unknown source or destination when applicable (see Table 1 Communication Status Key Conditions). (32) The MCS uses the contents of the data item referenced by dataname4 to indicate the number of filled character positions resulting from the execution of a RECEIVE statement (see 3.5 RECEIVE Statement).
As part of the execution of a SEND statement, the MCS interprets the contents of the data item referenced by dataname4 as the user's indication of the number of left-most character positions of the data item referenced by the corresponding SEND identifier that transmits the data (see 3.6 SEND Statement). (33) The content of the data item referenced by data name 5 can only be set by MCS as part of the result of executing a RECEIVE statement, and is set according to the following rules:
, when there is a RECEIVE MESSAGE phrase: 1) If the message group end is detected, the content of the data item referenced by data name 5 is set to 3. 2) If the message end is detected, the content of the data item referenced by data name 5 is set to 2. 3) If not a message is being transmitted, the content of the data item referenced by data name 5 is set to 0.
GB/T 4Q92- 13—92
When the RECEIVESEGMANT phrase is specified: h.
1) If the end of the message group is detected, the content of the data item referenced by data name 5 is set to 3. 2) If the end of the message is detected, the content of the data item referenced by data name 5 is set to 2. 3) If the end of the message segment is detected, the content of the data item referenced by data name 5 is set to 1. 4) If less than one message segment is transmitted, the content of the data item referenced by data name 5 is set to 0. When several conditions are met at the same time, the content of the data item referenced by data name 5 is determined by the rule that is met first in the list order. (34) The content of the data item referenced by data name 6 indicates the status condition of the previously executed DISABLEENABLE, PURGE, RECEIVE or SEND statement.
The actual relationship between the content of the data item referenced by data name 6 and the status condition itself is defined in Table 1 (Communication Status Key Conditions) below.
2.2.5 Communication Status Key Conditions
When the statements shown are completed, the following figure indicates the possible contents of the data items referenced by data name 10 in format 1, data name 3 in format 2, and data name 6 in format 3. The "×" on the row of the statement column indicates that the status key code shown in the row is possible for the statement. Symbol 2 indicates that the level 2 element is not available at level 1. Table 1
Communication Status Key Conditions
RECEIVE
SEND input-output-ud
Doutput-ed
AOCEPT MESSAGE COUNT
ENAHI.E INPUT
ENABLE INPL:T---O TERMINAL
ENABLE OLTPUT
DISABI.F INPUT
DISABLE INPUT-IO TERMINAL.
DISABLE
OLTPUT
STATUS KEY
No error found, action completed
Disconnect one or more destinations, action completed (see error key)Disconnect destination, no action
Symbol source, or one or more queues or destinations have been disconnected/connected (see error key)
One or more destinations are unknown, action completed for known destinations (see error key)
One or more queues or subqueues are unknown, no action is takenSymbol source is unknown, no action is taken
Destination count is illegal, no action is taken
Password is illegal, no connection/disconnection action occursBody length exceeds the length of identifier 1
Part of the message requested to be sent has a body length of zero or is missing identifier 1, no action is taken
Exceeds the capacity of the output queue (see error key)HECEIVE
SEND input-ouput-ud
SENDurpud
ACCEPT MESSAGE COUNT
2.2.6 Wrong key value
ENABLE INPUT
ENABILE INFUT>IO TERMINAT.
DISAHI.E INPUTIUTERMINAL
ENABLF OUTPUT
DISABLE INPI:T
GB/T 4092. 13- --92
Continued Table 1
DISABLE OUTPUT
Status value
One or more destinations do not have a partial message associated with them, and the action is completed for other destinations
A combination of at least two status key conditions 10, 15 and 20 has occurred, (see error key code)
Implementor defined status
The following Table 2 indicates the possible contents of the data item referenced by data name 4 in format 2 when the statements shown are completed. The × on the row of the statement column indicates that the relevant error key value indicated in the row is possible for the statement. Symbol 2 indicates a level 2 completion element that is not available in level 1
Table 2 Error key value
PCREG3
ENABLE
OUTPUT
3 Process part of the communication module
DISARLE OUTPLT:
Error key
No error
Symbolic destination unknown
3.1ACCEPTMESSAGE COUNT statement
3.1.1 Function
Symbolic destination disconnected
No message associated with the referenced symbolic destination"Symbolic destination connected/disconnected
Output queue capacity exceeded
Reserved for further use
Implementor-defined conditions
The ACCEITMESSAGECOLNT statement makes the count of complete messages in the queue available. 3. 1. 2
·General format
GB/T4092.13—92
ACCEPTcd name 1MESSAGECOUNT
3.1.3 Syntax rules
(1)cd name 1 must reference an input CD description item. 3.1.4 General rules
(1) The message count data item specified by the ACCEPTMESSAGECOUNT statement cd name 1 is modified to indicate the number of complete messages present in the queue structure, which is specified by the intimation of the data items specified by data name 1 (SYMBOLICQUEUE) to data name 4 (SYMHOLICSUB-QUEUE3) of the cd name 1 reference field. (2) When the ACCFI_IMESSAGECOUNT statement is executed, the content of the field specified by the communication description item must contain at least the message count. The symbol queue name to be tested. Testing this item causes the contents of the data item referenced by data item name 10 (STATUSKEY) and the contents of data name 11 (MESSAGECOUNT) in the fields associated with the communication description clause to be modified accordingly (see 2.2 Communication Description Clause). 3.2 DISABLE Statement
3.2.1 Function
The DISABIF statement informs the MCS to prohibit data transfer between the specified output queue and the destination for output, or to prohibit data transfer between the specified source and input queue for input, or to prohibit data transfer between the program and a specified source or destination for input and output. The WITIIKEY phrase is considered an obsolete element in this version of Standard COBOL because it was deleted in later revisions of Standard COBOL. 3.2.2 General Format
DISABLE I-0
TERMINAL
TERMINAL
lOUTPUT
3.2.3 Syntax Rules
ITHKEY
identifier1
value1
(1) When an INPUT statement is present, cdname1 must refer to an input CD description item. (2) When an I-0TERMINAL phrase is present, cdname1 must refer to an input/output CD description item. (3) When an OUTPUT phrase is present, cdname1 must refer to an output CD description item. (4) The content or value1 of the data item referenced by identifier1 must be defined as a character. 3.2.4 General Rules
(1) The DISABLE statement causes a logical disconnection between the MCS and the specified source or destination. When such a logical disconnection already exists, or if it has been handled by some other means outside this program, then the DISABLE statement is not required for this program. When a DISABLE statement is executed that specifies a disconnected source or destination, no further work is done except that the value in the status key data item indicates this condition. The DISABLE statement does not affect the logical path of data transmission between the COBOL program and the MCS. (2) The MCS ensures that execution of the DISABLE statement results in a logical disconnection at the source or destination when it is initially inactive. Execution of the DISABLE statement causes the transmission of the remainder of the message to never be stopped during the entry or termination of the transmission. (3) When the INPUT phrase is specified without the optional word TERMINAL, the logical path between the associated queues and subqueues and all possible associated sources as indicated by the contents of data name 1 (SYMBOL_CQUEUE) through data name 4 (SYMBOLICSUBQ)FUF-3 of the cd name 1 reference field is inactive. (4) When the INPUT phrase is specified with the optional word TERMINAL, the logical path between the source and all associated queues and subqueues as defined by the contents of the data item referenced by data name 7 (SYMBULICSOURCE) is inactive. (5) When the phrase I-0TERMINAL is specified, the logical path between the source and the program is inactive: the source is defined by the contents of the data item referenced by data name 3 (SYMBC>LTCTERMINAL). (6) When the phrase OUTPUT is specified, the logical path between all occurrences of data name 5 and up to and including the occurrence specified by the contents of data name 1 in the domain referenced by cd name 1 is inactive. (7) The contents of the data item referenced by word value 1 or identifier 1 must match the system password. The DISAB I.E. phrase is valid only if the contents of the data item referenced by word value 1 or identifier 1 match the system password. If the contents of the data item referenced by word value 1 or identifier 1 do not match the system password, the value of the STATUS KEY item in the domain referenced by name 1 is modified, and the MCS must process passwords containing from 1 to 10 characters. 3.3ENABIE Statement
3.3.1 Function
The ENABI.E statement informs the MCS to allow data transfer between a specified output queue and destination on output, between a specified source and input queue on input, or between a program and a specified source or destination on input and output. The WITHKEY phrase is considered an obsolete feature in this version of Standard COBOL because it will be deleted in future revisions of Standard COBOL.
3.3.2 General Format
ENABLEI-O
lOUTPUT
3.3.3 Syntax Rules
TERMINALI
TERMINAL
[WITHKEY|identifier]
Value -
(1) When the IVPUT phrase is specified, the name must refer to an input CD description item. (2) When the I-0TERMINAL phrase is specified, cd name 1 must reference an input-output CD description item. (3) When the (JUITPUT phrase is specified, cd name 1 must reference an output CD description item. (4) The value 1 or the content of the data item referenced by identifier 1 must be defined as a character type. 3.3.4 General Rules
(1) The ENABLE statement creates a logical connection between the specified source or destination and the MCS. When such a logical connection already exists or has been handled by some other section outside the program, the ENABLE statement in the program is not required. When an ENABLE statement specifying an already connected source or destination is executed, no other action is taken except that the value in the status key data item indicates this condition. The logical path of data transfer between the COBOL program and the MCS is not affected by the EVABLE statement. (2) When the INFUT phrase is specified without the optional TERMINAL, Then the contents of data name 1 (SYMBOLICQUEUE) to data name 4 (SYM13OI.ICSUB-QI:EUE-3) in the cd name 1 reference field indicate that the logical path between the relevant queues and subqueues and the relevant sources is active. (3) When the INPUT phrase with the optional word TERM1NAI is specified. The logical path between the source and all relevant queues and subqueues is active. This source is defined by the contents of the data item referenced by data name 7 (SYMB)LICS (URCE). (4) When the I-OTERMINAL phrase is specified, the logical path between the source and the program is active. This source is defined by data name 3 (SYM-ROLIC (5) When the (OUTPUT phrase is specified, the logical path is active for all locations specified by the content of each occurrence of dataname 5 up to and including the occurrence specified by dataname 1 in the domain referenced by cdname 1. (6) The content of the data item referenced by word value 1 or identifier 1 must match the password for entering the system. The EVABLE statement is valid only when the content of the data item referenced by word value 1 or identifier 1 matches the system password. If the content of the data item referenced by word value 1 or identifier 1 does not match the system password.Then modify the value of the STATUSKEY item in the domain referenced by cd name 1. MCS must be able to handle passwords from 1 to 10 characters.
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.