The SET Statement

ANS85The SET statement is used to alter the status of external switches.

ANS85The SET statement is used to alter the value of conditional variables.

VSC2MFThe SET statement is used to assign the address of a data item to a pointer data item. It is also used to adjust the contents of a pointer data item.

The SET statement establishes reference points for table handling operations by setting indices associated with table elements.

MFThe SET statement is used to assign the address of a program or an entry-point in a program to a procedure-pointer data item.

ISO2002MFThe SET statement is used to assign the address of a pointer to a program-pointer data item.

ISO2002MFThe SET statement is used to assign object references.

MFThe SET statement is used to alter the value of a synchronization data item.

MFThe SET statement is used to assign the address of a synchronization data item to another synchronization data item.

NET The SET statement is used to alter the size of a .NET native array.

NET The SET statement is used to initialize the contents of a .NET native array and to set the array size based on those contents.

NET The SET statement is used to alter the value of a boolean data item with usage CONDITION-VALUE.

NET The SET statement is used to alter the value of a data item with a .NET native type.

General Formats
ANS85Format 1 (Switch-setting)
ANS85Format 2 (Condition-setting)
VSC2Format 3 (Data-pointer-assignment)
ISO2002MFFormat 4 (Data-pointer-assignment)
ISO2002MFFormat 5 (Data-pointer-arithmetic)
Format 6 (Index-assignment)
Format 7 (Index-arithmetic)
MFFormat 8 (Procedure-pointer-assignment)
ISO2002MFFormat 9 (Object-reference-assignment)
MFFormat 10 (Value-of-Event-pointer)
MFFormat 11 (Address-of-Event-pointer)
MFFormat 12 (Value-of-Monitor-pointer)
MFFormat 13 (Address-of-Monitor-pointer)
MFFormat 14 (Value-of-Mutex-pointer)
MFFormat 15 (Address-of-Mutex-pointer)
MFFormat 16 (Value-of-Semaphore-pointer)
MFFormat 17 (Address-of-Semaphore-pointer)
NETFormat 18 (Size-of-array)
NETFormat 19 (Content-of-array)
NETFormat 20 (Boolean-setting)
NETFormat 21 (.NET-data-setting)
Directives
  1. In addition to Compiler directives which provide flagging and modify the reserved word list, the following directives may impact either the syntax or the semantics described in this section.
Syntax Rules
    All Formats
  1. The figurative constant NULL or NULLS or the data item referenced by pointer-name-2 or procedure-pointer-name-2 represents the sending area. ADDRESS OF identifier-2, ENTRY identifier-8, ENTRY literal-1 or the value held in the sending area, represents the sending value.

    The data item referenced by pointer-name-1, pointer-name-3 or procedure-pointer-name-1 or the COBOL system area implied by ADDRESS OF identifier-1 represents the receiving area.

    Identifier-3, integer-1 or LENGTH OF identifier-4 represents the increment value.

    2. Format 1
  2. ANS85Mnemonic-name-1 must be associated with an external switch, the status of which can be altered.

    MFSee the topic The Special-Names Paragraph for details of which external switches can be referenced in the SET statement.

    3. Format 2
  3. ANS85Condition-name-1 must be associated with a conditional variable.
  4. MFIf the FALSE phrase is specified, the FALSE phrase must be specified in the VALUE clause of the Data Description entry for condition-name-1.
  5. MFEach FALSE or TRUE phrase applies to the occurrences of condition-name-1 that precede that phrase and follow a previous FALSE or TRUE phrase, if any.
    6. Format 3 and 4
  6. VSC2MFIdentifier-1 must reference a level 01 or level 77 data item that is declared in the Linkage Section.

    OS390Identifier-1 must be declared in the Linkage Section, the Local-Storage Section or the Working-Storage Section

  7. ISO2002VSC2MFOS390Identifier-2 must reference a data item with a level of 77 or between 01 and 49 inclusive.

    ISO2002VSC2Identifier-2 must be declared in the Linkage Section.

  8. VSC2MFPointer-name-1, pointer-name-2 must each be an identifier that references an elementary data item with USAGE IS POINTER.
    9. Format 5
  9. MFPointer-name-3 must be an identifier that references an elementary data item with USAGE IS POINTER.
  10. MFIdentifier-3 must be an elementary numeric integer.
  11. MFInteger-1 may be signed.
    12. Format 6
  12. Identifier-5 and identifier-6 must each reference an index data item or an elementary item described as an integer. If both are specified, they must not both reference an elementary item.
    13. Formats 6 and 7
  13. Integer-2 and integer-3 may be signed. Integer-2 must be positive.
    14. Format 6
  14. Identifier-7 must reference an elementary numeric integer.
    15. Format 8
  15. MF Procedure-pointer-name-1 and procedure-pointer-name-2 must each be an identifier that references an elementary data item with USAGE IS PROCEDURE-POINTER.
  16. MFIdentifier-8 must be defined as an alphanumeric data item such that its value can be a COBOL or a non-COBOL program name.
  17. MFLiteral-1 must be a nonnumeric literal.
    18. Format 9
  18. ISO2002MFIdentifier-9 must be any item of class object that is permitted as a receiving item.
  19. ISO2002MFIdentifier-10 must be a class-name or an object reference; the predefined object reference SUPER must not be specified.
  20. ISO2002MFIf the data item referenced by identifier-9 is a universal object reference, the only predefined object references that may be specified for identifier-10 are SELF and NULL.
  21. ISO2002MFIf the data item referenced by identifier-9 is described with an interface-name that identifies the interface int-1, the data item referenced by identifier-10 must be one of the following:
    1. An object reference described with an interface-name that identifies int-1 or an interface inheriting from int-1.
    2. An object reference described with a class-name, subject to the following rules:
      1. If described with a FACTORY phrase, the factory object of the specified class must implement int-1
      2. If described without a FACTORY phrase, the instance objects of the specified class must implement int-1.
    3. An object reference described with an ACTIVE-CLASS phrase, subject to the following rules:
      1. If described with a FACTORY phrase, the factory object of the class containing the data item referenced by identifier-10 must implement int-1.
      2. If described without a FACTORY phrase, the instance objects of the class containing the data item referenced by identifier-10 must implement int-1.
    4. A class-name whose factory object implements int-1.
    5. The predefined object reference SELF, subject to the following rules:
      1. If the SET statement is contained in a method within the factory definition of the class, that factory definition must be described with an IMPLEMENTS clause that references int-1.
      2. If the SET statement is contained in a method within the instance definition of the class, that instance definition must be described with an IMPLEMENTS clause that references int-1.
    6. The predefined object reference NULL
  22. ISO2002MFIf the data item referenced by identifier-9 is described with a class-name, the data item referenced by identifier-10 must be one of the following:
    1. An object reference described with a class-name, subject to the following rules:
      1. If the data item referenced by identifier-9 is described with an ONLY phrase, the data item referenced by identifier-10 must be described with the ONLY phrase, and the class-name specified in the description of the data item referenced by identifier-10 must be the same as the class-name specified in the description of the data item referenced by identifier-9
      2. If the data item referenced by identifier-9 is described without an ONLY phrase, the class-name specified in the description of the data item referenced by identifier-10 must reference the same class or a subclass of the class specified in the description of the data item referenced by identifier-9
      3. The presence or absence of the FACTORY phrase must be the same as in the description of the data item referenced by identifier-9
    2. An object reference described with an ACTIVE-CLASS phrase, subject to the following rules:
      1. The data item referenced by identifier-9 must not be described with the ONLY phrase
      2. The class containing the data item referenced by identifier-10 must be the same class or a subclass of the class specified in the description of the data item referenced by identifier-9
      3. The presence or absence of the FACTORY phrase must be the same as in the description of the data item referenced by identifier-9
    3. The predefined object reference SELF, subject to the following rules:
      1. The data item referenced by identifier-9 must not be described with the ONLY phrase
      2. The class of the object containing the SET statement must be the same class or a subclass of the class specified in the description of the data item referenced by identifier-9
      3. If the data item referenced by identifier-9 is described without a FACTORY phrase, the object containing the SET statement must be an instance object
      4. If the data item referenced by identifier-9 is described with a FACTORY phrase, the object containing the SET statement must be a factory object
    4. A class-name, provided the data item referenced by identifier-9 is described with the FACTORY phrase, and class-name references the same class or a subclass of the class specified in the description of the data item referenced by identifier-9
    5. The predefined object reference NULL
  23. ISO2002MFIf the data item referenced by identifier-9 is described with an ACTIVE-CLASS phrase, the data item referenced by identifier-10 must be one of the following:
    1. An object reference described with the ACTIVE-CLASS phrase, where the presence or absence of the FACTORY phrase is the same as in the data item referenced by identifier-9
    2. The predefined object reference SELF, subject to the following rules:
      1. If the data item referenced by identifier-9 is described without a FACTORY phrase, the object containing the SET statement must be an instance object
      2. If the data item referenced by identifier-9 is described with a FACTORY phrase, the object containing the SET statement must be a factory object
    3. The predefined object reference NULL
    24. Format 10 (Value of Event-pointer)
  24. MF Event-pointer-1 must be defined as a data item with USAGE EVENT-POINTER.
    25. Format 11 (Address of Event-pointer)
  25. MFEvent-pointer-1 and event-pointer-2 must be defined as data items with USAGE EVENT-POINTER.
    26. Format 12 (Value of Monitor-pointer)
  26. MF Monitor-pointer-1 must be defined as a data item with USAGE MONITOR-POINTER.
  27. MFIf the NOT phrase is specified, then the CONVERTING phrase must not be specified.
    28. Format 13 (Address of Monitor-pointer)
  28. MFMonitor-pointer-1 and monitor-pointer-2 must be defined as data items with USAGE MONITOR-POINTER.
    29. Format 14 (Value of Mutex-pointer)
  29. MF Mutex-pointer-1 must be defined as a data item with USAGE MUTEX-POINTER.
    30. Format 15 (Address of Mutex-pointer)
  30. MFMutex-pointer-1 and mutex-pointer-2 must be defined as data items with USAGE MUTEX-POINTER.
    31. Format 16 (Value of Semaphore-pointer)
  31. MF Semaphore-pointer-1 must be defined as a data item with USAGE SEMAPHORE-POINTER.
  32. MFIdentifier-11 must reference an integer.
    33. Format 17 (Address of Semaphore-pointer)
  33. MFSemaphore-pointer-1 and semaphore-pointer-2 must be defined as data items with USAGE SEMAPHORE-POINTER.
    34. Format 18 (Size-of-Array)
  34. NETIdentifier-12 must be described with a format 3 OCCURS clause.
  35. NETIdentifier-13 must describe an integer.
  36. NETThe number of operands after the TO phrase must not exceed the number of dimensions specified for identifier-12.
    37. Format 19 (Content-of-Array)
  37. NETIdentifier-14 must be described with a format 3 OCCURS clause as either a one-dimensional array or a rectangular array.
  38. NETLiteral-2 must be a valid literal for a VALUE clause describing the subject of the entry.
  39. NETParentheses may be used within the repetitions of literal-2 to separate the values into subarrays.
    40. Format 20 (Boolean setting)
  40. NETIdentifier-15 and identifier-16 must have usage CONDITION-VALUE.
  41. NETCondition-name-2 and condition-name-3 must be associated with conditional variables.
  42. NETIf condition-name-2 is specified and the TRUE phrase is not specified, the FALSE phrase must be specified in the VALUE clause of the Data Description entry for condition-name-2.
    43. Format 21 (.NET-data-setting)
  43. NETIdentifier-17 is the receiving item.
  44. NETIdentifier-18, literal-3 or arithmetic-expression-1 is the sending item.
  45. NETThe SET statement is legal if any of the following are true:
    • Both the sending item and the receiving item are numeric
    • Identifier-17 and identifier-18 are objects of the same class.
    • The class of identifier-18 inherits directly or indirectly from the class of identifier-17.
    • Identifier-17 conforms to an interface and identifier-18 implements that interface.
    • There is an implicit conversion operator for an item with the class of identifier-18 to the class of identifier-17.
    • Identifier-17 is alphanumeric or national.
General Rules
    Format 1
  1. ANS85The status of each external switch associated with the specified mnemonic-name-1 is modified such that the truth value resulting from evaluation of a condition-name associated with that switch reflects an on status if the ON phrase is specified, or an off status if the OFF phrase is specified. (See the topic Switch-Status Condition in the chapter Procedure Division.)
    2. Format 2
  2. ANS85The literal in the VALUE clause associated with condition-name-1 is placed in the conditional variable according to the rules of the VALUE clause (see the section The VALUE Clause.) If more than one literal is specified in the VALUE clause, the conditional variable is set to the value of the first literal that appears in the VALUE clause.
  3. ANS85If multiple condition-names are specified, the results are the same as if a separate SET statement had been written for each condition-name-1 in the same order as specified in the SET statement.
  4. MFIf the FALSE phrase is specified, the literal in the FALSE phrase of the VALUE clause associated with condition-name-1 is placed in the conditional variable according to the rules for the VALUE clause. (See the topic The VALUE Clause.)
    5. Format 3 and 4
  5. VSC2MFThe sending value represents the address of a data item. If pointer-name-2 is specified, the sending value is the value contained with the data item referenced by pointer-name-2. If ADDRESS OF identifier-2 is specified, the sending value represents the address of identifier-2.
  6. VSC2MFIf pointer-name-1 is specified, the sending value is moved to the data name referenced by pointer-name-1.
  7. VSC2MFIf ADDRESS OF identifier-1 is specified, the sending value is moved to a COBOL system area and the runtime element subsequently operates such that the area of storage referenced by identifier-1 is located at the address represented by the sending value.

    MFWhether or not the link is retained between invocations of a subprogram is dependent on the STICKY-LINKAGE Compiler directive.

    8. Format 5
  8. MFBefore execution of the SET statement, the value of the data item referenced by pointer-name-3 must represent the address of a data item within a logical record, the original address. After execution of the SET statement, the value of the data item referenced by pointer-name-3 represents the new address. If the original address and the new address do not both lie within the same logical record, (or, for environments in which address space is segmented, within the same segment) then the results of using the value of the data item referenced by pointer-name-3 are undefined.
  9. MFIf the UP clause is specified, the new address is formed by adding the number of bytes given by the increment value to the original address.
  10. MFIf the DOWN clause is specified, the new address is formed by subtracting the number of bytes given by the increment value from the original address.
    11. Format 5
  11. The following steps are repeated for each recurrence of index-name-1 or identifier-5. Each time, the value of index-name-2 or identifier-6 is used as it was at the beginning of the execution of the statement. Any subscripting or indexing associated with identifier-5 is evaluated immediately before the value of that data item is changed.
    1. If index-name-1 is specified, index-name-1 is set to a value causing it to refer to the table element that corresponds in occurrence number to the table element referenced by index-name-2, identifier-6, or integer-2. If identifier-6 references an index data item, or if index-name-2 is related to the same table as index-name-1, no conversion takes place.
    2. If identifier-5 references an index data item, it can be set equal to either the contents of index-name-2 or identifier-6 where identifier-6 also references an index item; no conversion takes place in either case.
    3. If identifier-5 does not reference an index data item, it can be set only to an occurrence number that corresponds to the value of index-name-2. Neither identifier-6 nor integer-2 can be used in this case.
  12. The following table represents the validity of various operand combinations in the SET statement. The general rule reference indicates the applicable general rule.
    Sending Item Receiving Item
    Integer Data Item Index-Name Index Data Item
    Integer Literal No/11c Valid/11a No/11b
    Integer Data Item No/11c Valid/11a No/11b
    Index-Name Valid/11c Valid/11a Valid/11b1
    Index Data Item No/11c Valid/11a1 Valid/11b1
    Table 1: SET Index Statement Valid Operand Combinations

    1 = No conversion takes place.

    13. Formats 6 and 7
  13. Index-names are associated with a given table by being specified in the INDEXED BY phrase of the OCCURS clause for that table.
  14. If index-name-1 is specified, the value of the index after the execution of the SET statement must correspond to an occurrence number of an element in the table associated with index-name-1. The value of the index associated with an index-name after the execution of a PERFORM or SEARCH statement may be set to an occurrence number that is outside the range of its associated table. (See the topic The PERFORM Statement and the topic The SEARCH Statement.)

    If index-name-2 is specified, the value of the index before the execution of the SET statement must correspond to an occurrence number of an element in the table associated with index-name-1.

    If index-name-3 is specified, the value of the index both before and after the execution of the SET statement must correspond to an occurrence number of an element in the table associated with index-name-3.

    15. Format 7
  15. The contents of index-name-3 are incremented (UP BY) or decremented (DOWN BY) by a value that corresponds to the number of occurrences represented by the value of integer-3 or the data item referenced by identifier-7; thereafter, the process is repeated for each recurrence of index-name-3. For each repetition, the value of the data item referenced by identifier-7 is used as it was at the beginning of the execution of the statement.
    16. Format 8
  16. MFThe sending value represents the address of the start of a procedure within a COBOL or non-COBOL program.
  17. MFThe sending value is moved to the data item referenced by procedure-pointer-name-1.
  18. MFIf procedure-pointer-name-2 is specified, the sending value is the value contained within the data item referenced by procedure-pointer-name-2.
  19. MFLiteral-1 or the content of the data item referenced by identifier-8 is the name of the referenced procedure. If the referenced procedure is a COBOL procedure, the name of the referenced procedure must contain the program-name contained in the Program-ID paragraph of the referenced program or the entry-name contained in the ENTRY statement of the referenced procedure.

    MFIf the program being called is not a COBOL program, the rules for the formation of the program or procedure name are given in your COBOL system documentation on interfacing.

    MFIf the referenced procedure has been previously made available and remains available at the time of execution of the SET statement, then the sending value represents the address of the referenced procedure.

    MFIf the referenced procedure is not available at the time of execution of the SET statement, then the sending value represents the address of a COBOL system error procedure.

    20. Format 9
  20. ISO2002MFIf identifer-10 is an object reference, a reference to the object identified by identifier-10 is placed into each data item referenced by identifier-9 in the order specified.
  21. ISO2002MFIf identifier-10 is a class-name, a reference to the factory object of the class identified by identifier-10 is placed into each data item referenced by identifier-9 in the order specified.
    22. Formats 10 and 11
  22. MFIf more than one event-pointer-1 is specified, the results are the same as if a separate SET statement had been written for each event-pointer-1 in the same order as specified in the SET statement.
    23. Format 10 (Value of Event-pointer)
  23. MFThe execution of the SET statement sets the value of the event referenced by event-pointer-1 to TRUE or FALSE.

    MFNote: When an event is set to FALSE, the execution of any thread which executes a WAIT statement which references that event suspends until the event is set to TRUE in another thread.

    24. Format 11 (Address of Event-pointer)
  24. MFEvent-pointer-1 is set to reference the same event data item that event-pointer-2 references.
    25. Formats 12 and 13
  25. MFIf more than one monitor-pointer-1 is specified, the results are the same as if a separate SET statement had been written for each monitor-pointer-1 in the same order as specified in the SET statement.
    26. Format 12 (Value of Monitor-pointer)
  26. MFIf the NOT phrase is not specified, the value of the monitor referenced by monitor-pointer-1 is set to one of BROWSING, READING, or WRITING, thus establishing the corresponding form of lock. This specific lock type for this specific monitor must be eventually released by a SET statement either with a matching NOT phrase or a matching CONVERTING FROM phrase.

    For example, the lock established by

     SET mon-1 TO READING

    can be cleared by 

     SET mon-1 TO NOT READING
  27. MFThe CONVERTING phrase is used to change the current type of lock established on a monitor. The lock type specified in the FROM phrase must be currently established by that thread and upon successful execution of the statement, that lock will have been changed, in one atomic operation, to the lock type specified in the TO phrase.
  28. MFNested locks can be obtained by the execution of successive SET monitor statements with no intervening SET statement that releases the lock. Once a READING lock is established, no BROWSING or WRITING lock is allowed to nest within that thread. Once a BROWSING lock or a WRITING lock is established, any other level of lock is allowed to nest within that thread.
    29. Format 13 (Address of Monitor-pointer)
  29. MFMonitor-pointer-1 is set to reference the same monitor data item that monitor-pointer-2 references.
    30. Formats 14 and 15
  30. MFIf more than one mutex-pointer-1 is specified, the results are the same as if a separate SET statement had been written for each mutex-pointer-1 in the same order as specified in the SET statement.
    31. Format 14 (Value of Mutex-pointer)
  31. MFThe execution of the SET statement sets the value of the mutex referenced by mutex-pointer-1 to ON or OFF.
  32. MFWhen a mutex is set to ON, the execution of any thread that attempts to set that mutex to ON suspends until the mutex is set to OFF in the thread that set it ON.
    33. Format 15 (Address of Mutex-pointer)
  33. MFMutex-pointer-1 is set to reference the same mutex data item that mutex-pointer-2 references.
    34. Formats 16 and 17
  34. MFIf more than one semaphore-pointer-1 is specified, the results are the same as if a separate SET statement had been written for each semaphore-pointer-1 in the same order as specified in the SET statement.
    35. Format 16 (Value of Semaphore-pointer)
  35. MFThe contents of the semaphore data item referenced by semaphore-pointer-1 are incremented (UP BY) or decremented (DOWN BY) by a value that corresponds to the value of integer-4 or the data item referenced by identifier-11; thereafter, the process is repeated for each recurrence of semaphore-pointer-1. For each repetition, the value of the data item referenced by identifier-11 is used as it was at the beginning of the execution of the statement.
  36. MFIf a semaphore is set DOWN BY n and the semaphore is less than n, the thread is suspended until another thread raises the semaphore to above n.
    37. Format 17 (Address of Semaphore-pointer)
  37. MFSemaphore-pointer-1 is set to reference the same semaphore data item that semaphore-pointer-2 references.
    38. Format 18 (Size-of-Array)
  38. NETThe SET statement sets the size of the .NET array described by identifier-12 to the contents of the data item referenced by identifier-13 or the value of integer-5.
    39. Format 19 (Content-of-Array)
  39. NETThe SET statement creates an a .NET array of the size required to contain the values specified by the repetitions of literal-2 and initializes the array to the specfied values..
    40. Format 20 (Boolean setting)
  40. NETThe contents of the data-item referenced by identifier-15 or condition-item-2 is set to the contents of the data item referencesby identifier-16 or condition-name-3 or to TRUE or FALSE.
    41. Format 21 (.NET-data-setting)
  41. NETIf identifier-17 is alphanumeric or national, the ToString method is automatically invoked on the sending item and the resulting string moved to the data item referenced by identifier-17. Note that the ToString method exists for any class since it is implemented in System.Object.
  42. NETThe sending item is moved to the receiving item.