Difference: PUSHPOPILFStatements (16 vs. 17)

Revision 172008-10-06 - SteveFrizzell

Line: 1 to 1
 
META TOPICPARENT name="APPX500Features"

PUSH & POP ILF Statements

Line: 38 to 38
  The scope of a stack is the same as the scope of the associated field or file.  For example, if the scope of the referenced field is RELATED, then the scope of the associated stack will also be RELATED.
Changed:
<
<
The Data item type specification identifies which field value or record is to be pushed onto the stack.  If FIELD or RECORD is specified, then the  current value of the field or record is pushed onto the stack.  If DEFAULT FIELD or DEFAULT RECORD is specified, then the  default value of the field or record is pushed onto the stack.  If ORIGINAL FIELD or ORIGINAL RECORD is specified, then the original value of the field or record is pushed onto the stack.  ORIGINAL FIELD and ORIGINAL RECORD may only be specified if the process being executed has a PCF.
>
>
The Data item type specification identifies which field value or record is to be pushed onto the stack.  If FIELD or RECORD is specified, then the  current value of the field or record is pushed onto the stack.  If DEFAULT FIELD or DEFAULT RECORD is specified, then the  default value of the field or record is pushed onto the stack.  If ORIGINAL FIELD or ORIGINAL RECORD is specified, then the original value of the field or record is pushed onto the stack.  ORIGINAL FIELD and ORIGINAL RECORD may only be specified if the referenced field is a field in the PCF or if the referenced file is the PCF of the currently executing process.
 
Changed:
<
<
Since there is only one stack for each field name and one stack for each file name, FIELD, DEFAULT FIELD, and ORIGINAL FIELD all push the indicated values onto a common (shared) stack for the specified field name and RECORD, DEFAULT RECORD, and ORIGINAL RECORD all push the indicated record buffers onto a common (shared) stack for the specified record (file) name.
>
>
Since there is only one stack for each field name and one stack for each file name, FIELD, DEFAULT FIELD, and ORIGINAL FIELD all push the indicated value onto a common (shared) stack for the specified field name and RECORD, DEFAULT RECORD, and ORIGINAL RECORD all push the indicated record buffer onto a common (shared) stack for the specified record (file) name.
  Multiple occurrences of a field also share a common stack.
Line: 61 to 61
 (5) Data item type (FIELD, RECORD, DEFAULT FIELD, DEFAULT RECORD, ORIGINAL FIELD, ORIGINAL RECORD)
Changed:
<
<
A distinct stack is associated with each field name and with each file name.

The PUSH statement is used to add  field and record values to a stack.

>
>
The POP statement is used to pop (retrieve) a value that was saved with a PUSH statement.
 
Changed:
<
<
The POP statement is used to retrieve field and record values from a stack.
>
>
A distinct stack is associated with each field name and with each file name.
  The stack has the internal structure of a LIFO list, i.e. the last value pushed onto the stack for a field or record is the first value popped from the stack. There is no predefined limit as to how many field or record values may be pushed onto a stack.
Line: 73 to 71
  The POP statement sets the True/False indicator.  If the stack for the referenced field or file contains a value, then the stack is popped and the next level of the true/false statsu indicator is set to T (true).  If the stack is empty, then the referenced field is set to its default value and the next level of the true/false indicator is set to F (false).
Deleted:
<
<
The PUSH statement is used to PUSH the value of a field or record onto an internally maintained stack in memory.  The POP statement is used to POP (retrieve) a previously pushed value.
 Predefined fields may be referenced by a PUSH or POP statement. However, it is invalid to use the PUSH or POP statement for predefined fields that are non-modifiable.

The scope of a stack is the same as the scope of the associated field or file.  For example, if the scope of the referenced field is RELATED, then the scope of the associated stack will also be RELATED.

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback