Versions Compared

Version Old Version 28 New Version 29
Changes made by

Alex Roytman

Alex Roytman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Property nameProperty typeDescription
typeString

The following data types can be specified:

  • "packed decimal" or "packed" (both variations have the same meaning)
  • "decimal" or "zoned" or "zoned decimal" or "numeric" (all variations have the same meaning)
  • "integer"
  • "unsigned integer"
  • "char"
  • "boolean"
  • "date"
  • "time"
  • "timestamp"
  • "pointer"
  • "data structure"

Some config properties only apply to certain types.

lengthNumber

Specifies the field length. It is required for most data types; exceptions are:

  • date
  • time
  • timestamp
  • pointer
  • data structure
decimalsNumber

Specifies the number of decimal positions. It required for packed and zoned fields.

varyingBooleanSpecifies that a character field is of varying length; otherwise, the field will be a fixed length field padded with spaces.
initValueString/Number/Boolean/ArraySpecified the field's initial value.
dimNumberAvailable to all data types. Using dim makes your field This property turns the definition into an array. Arrays are 1-indexedWhen declared this way, arrays start with an index of 1, similar to RPG.
orderByString

Available to all types when dim element is used. Either of these values are requiredSpecifies the default sort order for arrays declared with the dim property. The orderBy property is used by array-related API, such as pjs.lookup().

Possible values are:

  • "ASCEND"
  • "DESCEND"
elementsObjectRequired when using data-structure type. Read about data-structures belowSpecifies an object of subfields for a data structure. Each property within the object is the subfield name, while the property value is another config object.
qualifiedBooleanAvailable when using data structure type

Identifies a data structure as qualified, meaning that all references to its subfields must be qualified with the data structure name first; for example: MyDS.mysubfield = "myvalue".

If qualifies is not specified, the subfields can be referenced directly; for example: mysubfield = "myvalue".

specialString

Available to data-structure subfields. Acceptable values are:

PSDS

  • "*status"
  • "*proc"
  • "*parm"
  • "*routine"

INFDS

  • "*file"
  • "*record"
  • "*opcode"
  • "*status"
  •  "*routine" 
nullableBoolean / String

Use this property to create null-capable fields.

  • Pass in true to make the field null-capable. This option also allows you to assign a null value to the field.
  • Pass in a string, which references a Boolean field to use as the null-indicator and makes the field null-capable.
likeRecObject

Available when using a data structure type. This object requires two elements.

  • intrecname - String, name of record format from previously defined table.
  • fields - optional String value of "*key". If "*key" is specified, only key fields will be defined.

When likerec is specified, the data structure becomes qualified automatically.

likeDSStringUsed on a data structure to specify the name of another data structure from which the configuration is derived.
dataAreaString

Available to all data types, except from the pointer type. String pointing to data-area object. Example values:

  • MYDTAARA
  • PRODLIB/DTAATA
statusDSBooleanIdentifies a Status Data Structure. A Status Data Structure is automatically populated with information about the current Profound.js module and job. It is an easy way to retrieve information, such as the current IBM i job name, the current user id, and more.

...