Release notes for Model 204 version 7.5

From m204wiki
Jump to navigation Jump to search

These release notes list the enhancements and other changes contained in Model 204 version 7.5, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

Overview

These release notes contain installation and features information for the Rocket Model 204 version 7.5.0 release. Before beginning your installation, please read through this information about product installation and changes.

New in this release

This section summarizes the new features and enhancements for Model 204 version 7.5.0.

SOUL (User Language)

The significantly enhanced, object-oriented, version of User Language is now called SOUL. All existing User Language programs will continue to work under SOUL, so User Language can be considered to be a subset of SOUL, though the name User Language is now deprecated.

FeatureOperating System
Sirius object-oriented language extensions integrationz/VM, z/OS, z/VSE
ECF statements can pass up to 60 parametersz/VM, z/OS, z/VSE

System Management

FeatureOperating System
Writing records to the SMF data set without an SVC installedz/VM, z/OS, z/VSE

Performance

FeatureOperating System
GTBL can be stored above the barz/VM, z/OS, z/VSE

Operating system requirements

Requirements for Model 204 version 7.5.0 are still being determined.

Model 204 version 7.4.0 required the following operating system support:

  • For IBM z/OS: Version 1 Release 7 is sufficient for all new functionality except for the following features:
    • Large (1 MB) page support requires Version 1 Release 9.
    • Extended address volumes (EAV) requires Version 1 Release 12.
  • For IBM z/VM: Version 5 Release 4.0 or later
  • For IBM z/VSE:
    • Version 5 Release 1 or
    • Version 4 Release 3 or
    • Version 4 Release 2.1 or
    • Version 4 Release 2.0, with these program temporary fixes (PTFs) installed:
      • UD53436
      • UD53437
      • UD53438
      • UD53439

Hardware requirements

Requirements for Model 204 version 7.5.0 are still being determined.

Model 204 version 7.4.0 required the IBM z/890 or above processor, except for the following feature:

The large (1 MB) page support feature requires the IBM z10 or above processor.

Model 204 compatibility with operating systems

Content in this section is still to be determined.

Model 204 compatibility with Connect*

All supported versions of Connect* are compatible with Model 204 version 7.5.0. However, CLOB/BLOB support requires Connect* version 7.4.0 or higher. Use of Connect* versions earlier than version 7.4.0 to SELECT, UPDATE, or INSERT CLOB/BLOB data will fail and might produce unexpected application behavior and/or return an error. Connect* version 7.5.0 is compatible with versions of Model 204 that are earlier than version 7.5.0.

SOUL (User Language) enhancements

Much of the substantial new and enhanced functionality described in the following subsections is available as a result of the acquisition of Sirius Software. The functionality that is the subject of the initial subsection, "Object oriented programming," motivates the new name for User Language, SOUL, often thought of as Simple Objective User Language.

Object oriented programming

As of version 7.5 of Model 204 (and backward compatible with existing User Language applications), the SOUL language is equipped with Object-Oriented Programming (sometimes abbreviated O-O) capabilities comparable or superior to other contemporary object oriented languages. Formerly contained in the Janus SOAP User Language Interface, you can use Janus SOAP ULI essentials as a set of entry points to the extensive SOUL O-O documentation.

Record capacity increase

in this version of Model 204, the record limit is increased from sixteen million records to forty-eight million records per file.

New SOUL statements

Non O-O enhancements in SOUL

External Call Facility (ECF)

EXTERNAL CALL statements can now pass more parameters. The maximum number of parameters that can be passed in an EXTERNAL CALL statement has been increased from 40 to 60. The maximum value setting for ECPSIZE is increased from 1310680 to 1966020 to accommodate the extra parameters.

REPEAT statement UNTIL option

The REPEAT statement now supports the UNTIL option. In previous releases, only REPEAT WHILE was supported.

A REPEAT UNTIL enters the loop body prior to checking the condition.

Example:

The following program results in output of '1':

BEGIN REPEAT WHILE %I EQ 0 %I = %I + 1 PRINT %I END

However, the following program results in an endless print loop:

BEGIN REPEAT UNTIL %I EQ 0 %I = %I + 1 PRINT %I END

New and changed classes and methods

New HttpRequest TranslateTable property

The TranslateTable HttpRequest property makes it possible to set the translate table to be used for EBCDIC to ASCII translation of data in an HttpRequest object.

New InvalidTranslateTable class

Objects of the InvalidTranslateTable exception class are thrown when a requested system translate table cannot be found. It is currently thrown only by the TranslateTable HttpRequest property.

New bit manipulation String functions

New bit manipulation functions BitClearString, BitCountString, BitFlipString, BitSetString, and BitValueString make it easier to manipulate the bits in a string.

New InvalidBitNumber class

Objects of the InvalidBitNumber exception class are thrown when an invalid bit number is requested by a bit manipulation function. It is currently thrown only by the BitClearString, BitFlipString, BitSetString, and BitValueString functions.

New option for AppendJournalData

The QT option is added to the AppendJournalData method, to include QT type audit entries.

New parameter for AddField

The Strip option is added to the Screen class method AddField to allow suppression of leading and trailing blank removal from input fields.

New and changed $functions

Former Sirius $functions

The $functions referred to by the link below are added to SOUL as a result of the acquisition of Sirius Software:

$SNDMAIL attachment ASCII translation

The $SNDMAIL function can now translate an attachment to ASCII before sending it. This translation is useful if the $SNDMAIL attachment is a CLOB (CHARACTER-LARGE-OBJECT) such as a text document.

The $SNDMAIL function now accepts an optional parameter after the name of the attached object. If this parameter is set to 'C' (or to a percent variable with the value 'C'), the object in the buffer is translated to ASCII before being attached to the email.

If this parameter is not specified, the object in the buffer is sent as a binary object.

In this example:

%RC = $SNDMAIL(%SUBJECT,,%BODY,%FROM,%TO,,,,'CLOB.TXT','C')

the CLOB.TXT attachment will be translated to ASCII before being attached to the email.

New products

These products are now available to Model 204 customers as separately purchased items as a result of the acquisition of Sirius Software.

File-related enhancements

Repeating field groups

[placeholder for long section to come from 7.2 rel notes]

Increased Table B record number capacity

Table B can now contain up to 48M possible record numbers. (The previous limit was 16M.)

Set FILEORG=X'200' at file creation time to allow for the increased record numbers.

Notes

  • The limit for BSIZE remains at 16M.
    BSIZE * BRECPPG must be less than or equal to 48M (actually decimal 50,331,648 to be exact).
    For example, if BSIZE = 16M, BRECPPG cannot be more than 3.
  • FILEORG=X'200' cannot be specified for files with hash key or sorted file organization.

System management enhancements

Writing records to the SMF data set

Having Model 204 write records to the SMF data set no longer requires the installation of an SVC.

Therefore, the SMFSVC parameter is no longer required and, if present, will be ignored and flagged with the following informational message:

M204.0204: PARAMETER SMFSVC OBSOLETE AND NOT RESET

However, the SMFLORN and SMFSLRN parameters must still be present in CCAIN if SMF records are required.

Performance enhancements

GTBL in above the bar storage

GTBL can now be placed into non-swappable server storage area above the bar. In order to store GTBL in ATB storage:

  • Increase the SERVNSSZ parameter by the GTBL size.
  • Set the second byte of the SERVNSA parameter to X’80’, so the value of SERVNSA is X'00800000'.

Note: The settings for each server table above the bar are independent of each other. So if both FTBL and GTBL are placed above the bar, then SERVNSA should be set to X'02800000'.

NTBL,FTBL, QTBL in above the bar storage

Needs details . . .

MQ/204 enhancements

Freeing MQ/204 subtasks and associated storage

The new MQDELDTP PST (pseudo subtask) checks for MQ/204 subtasks that are in a delayed detach state. MQDELDTP detaches MQ/204 subtasks that have finished their work and releases their associated storage areas.

Other features

AT-MOST-ONE and field groups

The AT-MOST-ONE attribute is now applicable to a field group definition.

Storing and updating LOBs

All large object data (LOBs) in a FILEORG=X’100’ file are chained. There are four bytes per Table E page overhead for chained LOBs. The pages used by a chained LOB are not contiguous.

Handling LOBs in FILEORG=X’100’ files also has the following effects:

  • The RESERVE clause is ignored in a LOB field ADD statement processing, as well as the STORE RECORD statement processing of fieldname=value pairs. Consequently, the CHANGE statement does not fail because of insufficient reserved space. If the CHANGE statement requires that a LOB field be extended, it is.
  • The value of the EHIGHPG parameter is always one less than the high water mark of the number of pages used to hold LOBs. (Unless none were ever added, in which case it is zero, not -1).
  • The value of the EPGSUSED parameter is always the number of pages currently being used to hold LOBs.
  • The COMPACTE command does not process FILEORG=X’100’ files, just as it does not process a file created in V6R1 or earlier. Thus, issuing a COMPACTE command for a FILEORG X’100’ file produces an error message.
  • The TABLEE command effectively does a VIEW ESIZE EHIGHPG EPGSUSED for a FILEORG X’100’ file. Consequently there are no TABLEE overhead pages in a FILEORG=X’100’ file.

Constraint attributes

You can set range constraints on fields using the constraint attributes. Each set of range attributes is comprised of four attributes (GE, GT, LE, LT) that you can use to establish a range for integer values, float values, or date-time stamp values. The types of range attributes are mutually exclusive. For example, you cannot define a field with the FLOAT-GE and INTEGER-LE attributes.
When a range constraint is redefined, it replaces the existing field constraint.

Note:
The range constraints do not have to match the data type of the stored field. That is, you could have a date/time constraint for a STRING field or an integer constraint for a FLOAT field, and so on.

You can set the following constraint attributes:

  • date-time value
  • pattern for a field value
  • length
  • integer value

See Content Constraints for details.

CHUNK attribute for improved range searching on ORDERED NUMERIC fields

The CHUNK field attribute enables more efficient range searching on numeric ordered index (ORDERED NUMERIC) fields. CHUNK improves performance of the "RANGE" and "BETWEEN" FIND terms. A CHUNK field defines a subrange ("chunk") of the data range. Searching by chunks on a range of data requires fewer scans of the ordered index entries to find the desired data. Once CHUNK fields are defined, they are automatically used by FIND processing, so no application code needs to be changed.

After defining an ORDERED NUMERIC field, you define one or more related CHUNK fields containing data from the original base field rounded down by a specified CHUNK size.

Example:

DEFINE FIELD YYYYMMDD WITH ORDERED NUMERIC DEFINE FIELD YYYYMM WITH ORDERED NUMERIC INVISIBLE CHUNK 100 FOR YYYYMMDD DEFINE FIELD YYYY WITH ORDERED NUMERIC INVISIBLE CHUNK 10000 FOR YYYYMMDD

CHUNK requires FILEORG=x'100' and the INVISIBLE and ORDERED NUMERIC field attributes. See CHUNK attribute for details.

Upward compatibility issues

Change to the Ordered Index layout

Formerly all ORDERED NUMERIC fields came after all ORDERED CHARACTER fields in the Ordered Index. Now, the fields are interspersed in field code order.

ZFIELD Image

The ZFIELD image has been updated for this release. The image is used with $LSTFLD and $FDEF function calls.

INTERCOMM is no longer supported

The INTERCOMM interface supports the use of Teletype and 3270 terminals in line-at-a-time mode, using the Model 204 IODEV=29 thread type.

INTERCOMM is not supported in Model 204 version 7.5.

See the Rocket Model 204 Terminal User's Guide for a discussion of terminal interfaces.

User PDL overflow

The new SEQPDL parameter might require you to increase the size of the user Push Down List (using UTABLE LPDLST) by up to 3072 bytes, or more if you specify a value for SEQPDL that is larger than the 4096 default value.

New and changed commands

DEFINE FIELD new COMMA option

The COMMA option on the DEFINE FIELD command uses commas to separate displayed field attributes.

UNICODE codepage 1154 for Cyrillic

The UNICODE command now accepts 1154 as a codepage name. This codepage has 92 Unicode characters in the range U+0400 through U+045F, representing the Basic Russion alphabet and all of the Cyrillic extensions excepting the four which have grave accents.

Reliability enhancements

SEQPDL parameter

The new SEQPDL parameter controls the amount of free space that must be present in the user's Push Down List (PDL) in order for the SOUL sequencer to proceed with the next quad code. The minimum and default value is 4096 bytes. The maximum value is 8192 bytes. SEQPDL is a user resettable parameter and can be set on the user's parameter line or reset with the UTABLE command.

Formerly 1024 bytes of PDL free space were hardcoded internally in the Model 204 core. With 1024 bytes there were edge cases where abends would break files, resulting in ERROR 2126 USER'S PUSHDOWN LIST OVERFLOWED. SEQPDL is provided to allow enough PDL space so that all of the lower level journaling routines can process error conditions without breaking files.

If your applications are using close to the amount of PDL space currently set by the LPDLST value, you might need to increase LPDLST to reflect SEQPDL's increase in free space.

New and changed parameters

In addition to the following specific parameter changes, Model 204 parameter descriptions, for example as displayed by the VIEW command, are now in mixed case (unless translated to uppercase due to UPCASMSG.)

ECPSIZE max value increase

The maximum value setting for ECPSIZE has been increased from 1310680 to 1966020 to accommodate more External Call Facility parameters.

FILEORG change

The FILEORG X'100' setting for enhanced data handling files is available as of Model 204 version 7.5.

X'100' enables a number of enhancements to the file structure, including support for physical field groups; the definition of up to 32000 fields in a file; system maintained Automatic fields; Field Constraints providing content validation; and improved space management of fields containing Large Objects.

If X'100' is selected, the X'80' bit (optimized field extraction files) is automatically set.

MODTIM parameter (new)

The MODTIM system parameter displays the most recent assembly date and time of the Model 204 load module.

OUTPUT=DUMMY for IODEV=3 threads

IODEV=3 threads definitions now allow OUTPUT=DUMMY. When defining IODEV=3 threads, if output is not required, the OUTPUT parameter can be coded as OUTPUT=DUMMY.

For example:

IODEV=3,INPUT=IOD3IN1,OUTPUT=DUMMY

This means that no DD statement is required for the output data set, and in cases where many IODEV=3 threads are defined to simulate a large number of users, this enhancement will reduce the number of DD statements required by one half.

RESPAGE parameter (new)

Activates the APSY Precompiled Procedures in storage feature using above the bar pages by specifying a number of 4K operating system pages.

RETRVKEY parameter change

New in this release, if you specify a non-zero setting of RETRVKEY:

  • If you have set the X'01' or X'10' bits of the RETRVOPT parameter, you can use a forward retrieve PF key, in addition to the backward retrieve PF key specified by RETRVKEY.

    Note: If either of these bits is set, the X'02' bit is strongly recommended as well.

  • The size of the allocated storage area, and hence the number and length of input lines available for retrieval, is specified by the value of the RETRVBUF parameter.


SEQPDL parameter (new)

The SEQPDL parameter controls the amount of free space that must be present in the user's Push Down List in order for the SOUL sequencer to proceed with the next quad code. SEQPDL allows enough PDL space for the lower level journaling routines to handle error conditions properly without breaking files and causing ERROR 2126 USER'S PUSHDOWN LIST OVERFLOWED.

SESMAXTO parameter (new)

The SESMAXTO parameter can be used limit the maximum session timeout value or to cause all current closed sessions to be immediately discarded.

UPCASMSG parameter (new)

The UPCASMSG parameter can be used to translate messages issued by Model 204 to uppercase; otherwise (depending on the message being issued) they are displayed in mixed (upper and lower) case.


New and updated messages

M204.0141:
BUG .. DUPLICATE FILE NAME IN CP RECORD

Explanation: A duplicate file name was encountered while attempting to add a deferred update dataset to the file directory during recovery. This indicates a potential problem in the Model 204 software.

System Manager Response: Contact Customer Support with the following documentation:

  • Audit trail from the previous run
  • Journal from the previous run

Return Codes: E 0 4 AD OPR

M204.0204:
PARAMETER SMFSVC OBSOLETE AND NOT RESET
Explanation: Writing records to the SMF data set no longer requires the installation of an SVC. The SMFSVC parameter is therefore obsolete and cannot be reset.
System Manager Response: No response required.
Return Codes: I 0 0 AUDITMS

Messages M204.0332 and M204.0336 indicate problems with the CRAM interface. The visibility of these messages has been improved by:

  • writing the message to the operator and the JESLOG
  • writing the message as an ER line in CCAAUDIT
  • setting the return code to 80

M204.0332:
RC nn FROM CRFS OPEN
Explanation: The run has failed to initialize due to problems with the CRAM interface. The possible formats of this message are:

Format 1: RC nn FROM CRFS OPEN/PUT/GET

Format 2: ECB postcode FROM CRFS PUT/GET

  • Format 1 indicates that Model 204 module CRFS attempted to open channel, send a message down the channel, or receive a message from a channel. CRAM was unable to satisfy the request. The message states the return code and the operation attempted.
  • Format 2 indicates that Model 204 module CRFS received an unexpected post code from CRAM while attempting an I/O operation on a channel. The message states the post code and the operation attempted.

System Manager Response: Contact Technical Support and have the audit trail available.
Return Codes: C 80 80 AUDITER NOTERM OPR

M204.0336:
RC nn FROM CRIO OPEN
Explanation: The run has failed to initialize due to problems with the CRAM interface. The possible formats of this message are:

Format 1: RC nn FROM CRIO OPEN/PUT/GET

Format 2: ECB postcode FROM CRFS PUT/GET

  • Format 1 indicates that Model 204 module CRIO attempted to open a channel, send a message down a channel, or receive a message from a channel. CRAM was unable to satisfy the request. The message states the return code and the operation attempted. For example, the return code 16 indicates that the CRAM channel is already open.
  • Format 2 indicates that Model 204 module CRFS received an unexpected post code from CRAM while attempting an I/O operation on a channel. The message shows the post code and the operation attempted.

System Manager Response: Contact Technical Support and have the audit trail available.
Return Codes: C 80 80 AUDITER NOTERM OPR

M204.0434:
NJBUFF SET TO %C

Explanation: TBD

M204.0761:
ATRPG*ASTRPPG EXCEEDS maxentries

Explanation: You attempted to initialize a file that was created with invalid parameters. The number of dictionary entries is determined by the product of the parameters ATRPG and ASTRPPG. The maximum allowed product is 4000, or 32000 for a FILEORG=x'100' file. The INITIALIZE command is rejected.

Response: The file must be recreated. Retry the CREATE command specifying ATRPG and ASTRPPG parameter values such that the product of the two is less than maxentries.

C 0 4 AUDITER

M204.0790:
FILE TOO BIG
Explanation: The total number of records possible in Table B exceeds 342 segments for files that do not have the FILEORG X'200' bit set and 1024 segments for files that have the FILEORG X'200' bit set. The number of potential record numbers per segment is 49,152. The number of possible segments in Table B is calculated by the following formula:

((BSIZE * BRECPPG) / 49,152)) + (1 if remainder not 0)

If the result exceeds 342 or 1024 respectively too many segments result and MODEL 204 rejects the CREATE command.
File Manager Response: Make the file smaller (by specifying a smaller BSIZE or smaller BRECPPG), or divide the file into smaller pieces and use the file group feature to process them as a single logical file.
Return Codes: C 0 4 AUDITER

M204.0797:
BSIZE*BRECPPG EXCEEDS MAXIMUM VALUE
Explanation: The product of BSIZE and BRECPPG must not exceed 16,777,216 for regular Model 204 files (which do not have the FILEORG X'200' bit set) and 50,331,648 for files that have the FILEORG X'200' bit set. These numbers specify the maximum number of records allowed in a single Model 204 file.

The CREATE or INCREASE command is rejected.
File Manager Response: Retry the command, specifying values for BSIZE and BRECPPG so that BSIZE*BRECPPG does not exceed the limit. Refer to the Rocket Model 204 File Manager's Guide for more information on file sizes.
Return Codes: C 0 4 AUDITER

M204.1052:
LOUTPB %C TO %C
Explanation: LOUTPB has been increased or decreased, to the value given in the message. With a full-screen terminal the value is 1.5 times the minimum for that model number, rounded up to a multiple of 8. A model 2 terminal results in a LOUTPB of 3200. A model 5 terminal results in a LOUTPB of 5664.

If NBKPG is greater than 0, the largest allowable value for LOUTPB is PAGESZ minus 40, so the value can be decreased for this reason.

User Response: No response is needed. This message is for information only.
Return Codes: I 0 0 AUDITAD

M204.1060:
%C NOT ALLOWED WITH NON SWAPPABLE SERVERS

Explanation: The service requested is not compatible with non-swappable servers.

System Manager Response: Remove any non-swappable server settings and restart Model 204 to repeat the service.

Return Codes: E 0 4 AUDITMS

M204.1131:
CAN'T action
Explanation: The procedure action cannot be taken for one of the following reasons:

  • The procedure is in use by another user.
  • The procedure is not in the file.
  • The user does not have the correct privileges to change the procedure.
  • If a RENAME or ASSIGN has been attempted, the alias might already exist.

Response: Make sure that the procedure name is spelled correctly. If the named procedure is in use, retry the command when the procedure is no longer in use. Otherwise, arrange to place the procedure in the file or to obtain the privileges to change the procedure.
Return Codes: C 0 4 SUFFIX AUDITER

M204.1260:
[FIELD | FIELDGROUP] WAS PREVIOUSLY DEFINED WITH DIFFERENT ATTRIBUTES, NEW [FIELD | FIELDGROUP] OPTIONS IGNORED

Explanation: A DEFINE [FIELD | FIELDGROUP] command has attempted to define an existing field with different attributes.

Response: If you wish to redefine the attributes of the field, you must issue the REDEFINE [FIELD | FIELDGROUP] command. Notify your file manager.

Return Codes: C 0 4 AUDITER

M204.1307:
%C LOGON REJECTED - reason text (REASON CODE: %X)

Explanation: The MODEL 204 3270 terminal handler has rejected a logon request from a 3270 terminal for the reason stated. The following reason codes are defined:

  1. There are no control blocks available for new logons. Increase the number of IODEV 7 terminal definitions. The reason text is: NOT ENOUGH 3270 TERMINALS.
  2. The terminal has been defined with a non-3270 transmission services profile. The LU type must be 2. The reason text is: LU TYPE NOT = 2.
  3. The terminal has been defined to require definite responses to messages it sends inbound to the host. The transmission services profile must be 3.
    The reason text is: TS PROFILE NOT = 3.
  4. There has been an error on this terminal. This is a retryable error. The reason text is: LOSTERM SET FOR THIS TERMINAL.
  5. The terminal definition is in use. This error should not occur. The reason text is: TERMINAL ALREADY IN USE.

System Manager Response: Contact your VTAM systems programmer to correct the VTAM definition.

Return Codes: E 0 4 AD SAVE NOTERM OPR

M204.1346:
SERVER AREA GREATER THAN CYLINDER CAPACITY FOR THIS DEVICE. CYLINDER SIZE = nnn BYTES.

Explanation: The number of bytes specified for the largest server area (SERVSIZE) is greater than nnn, the number of bytes contained in a cylinder for the type of disk device on which your CCASERVR (CCASRVR for DOS) data set resides.

System Manager Response: Do one of the following:

  • ensure that the largest SERVSIZE value does not exceed nnn
  • place your server data sets on a type of disk device that has a larger cylinder capacity
  • place CCASERVR in storage. (See the "CCASERVR in Storage feature" section in the Rocket Model 204 System Manager's Guide.)

Return Codes: C 96 96 AUDITER

M204.1381 is a new informational message issued during REGENERATE to help verify that the journal data provided in CCAGEN is from the correct CCAJRNL. The 58 bytes printed are the journal header of each journal block as described in the Rocket System Manager’s Guide, Using System Statistics chapter, Table A-2. The message has three variations:

  • M204.1381:
    CCAGEN: FIRST 5 CCAJRNL BLOCKS + LAST BLOCK IN HEX

    Explanation: The first 58 bytes, in hex, of the first five CCAJRNL blocks and the last CCAJRNL block read from CCAGEN follow in CCAAUDIT.

  • M204.1381: PASS1: 006000020113214F155421910000000000CB... M204.1381: PASS1: 0AD000020113214F155421910000000100CB... M204.1381: PASS1: 07BF008A0113214F155421920000000200CB... M204.1381: PASS1: 0B5E00020113214F155422000000000300CB... M204.1381: PASS1: 0AAF00120113214F155422030000000400CB... M204.1381: LASTB: 00C900020113214F155930280000337100CB...

    Explanation: This is an example of the first 5 CCAJRNL blocks and the last block read from CCAGEN during pass 1 of REGENERATE.

  • M204.1381:
    CCAGEN BLOCK COUNT: nnnn

    Explanation: This message provides the count of CCAJRNL blocks read from CCAGEN.

    • Response: This message is informational only; no response is required.

    Return Codes: 1 0 0

    The following new message replaces

    M204.1070: ALLOCATE FAILED - reason

    with additional information regarding the failure of the ALLOCATE command. However, M204.1070 remains in use by Janus/TCPIP for a different purpose.

    M204.1387:
    ALLOCATE failed; DDNAME=ddname,DSNAME=dsname could not be located

    Explanation: An attempt to allocate an existing data set, data set name=dsname, failed because the specified dsname was not found in the catalog or the catalog could not be accessed.

    Response: Correct the data set name or ensure that the data set exists and is cataloged.

    Return Codes: C 0 4 AUDITER

    M204.1393:
    CHUNK clause not of format "CHUNK chunkSize FOR chunkTarget"
    Explanation: On a DEFINE FIELD, the syntax of the CHUNK clause was not in the format shown in this message.
    File Manager Response: Correct the DEFINE FIELD command that has the incorrect CHUNK clause syntax.
    Return Codes: C 0 4 AUDITER

    M204.1394:
    CHUNK chunkSize VALUE INVALID: reason
    Explanation: On a DEFINE FIELD, the value specified for the size of a CHUNK is invalid; "reason" indicates why.
    File Manager Response: Correct the DEFINE FIELD command that has the invalid CHUNK size.
    Return Codes: C 0 4 AUDITER

    M204.1395:
    CHUNK target field invalid type: reason
    Explanation: On a DEFINE FIELD, the field specified as a CHUNK target is not a field type that can be used as a chunk target, for the reason specified.
    File Manager Response: Correct the DEFINE FIELD command containing the invalid CHUNK target type.
    Return Codes: C 0 4 AUDITER

    M204.1396:
    CHUNK fields must be INVISIBLE ORDERED NUMERIC
    Explanation: On a DEFINE FIELD, an attempt was made to create a CHUNK field that was not INVISIBLE ORDERED NUMERIC, which is a requirement of chunk fields.
    File Manager Response: Correct the DEFINE FIELD command that has the invalid CHUNK target type.
    Return Codes: C 0 4 AUDITER

    M204.1397:
    A CHUNK field was defined, %F may no longer be opened with M204 releases prior to V7R5
    Response: This is an informational message. No action is required.
    Return Codes: I 0 0 AUDITMS

    M204.1489:
    NOT ENOUGH FILE SPACE TO CONTINUE PROCEDURE DEFINITION - %F

    Explanation: There is no room in the file to store the procedure being entered with the PROCEDURE command.

    If…Then Model 204…
    Error occurs after the first line of procedure text has been storedKeeps the partial procedure
    You are entering the text at your terminalEnds procedure definition immediately
    Procedure text is supplied by another procedureFlushes the remainder of the input
    Procedure text is supplied in a batch input stream (CCAIN)Flushes the remainder of the procedure text and resumes processing after the END PROCEDURE command

    Response: Create space in the file by deleting unwanted procedures or increasing Table D with the INCREASE command. Replace the partial procedure using the PROCEDURE command, or use the EDIT command to supply the missing text.

    Return Codes: C 0 4 CANCEL AUDITER

    M204.1587:
    FSCB full, IMAGE too large: LFSCB required = num, bytes available in FSCB = num

    Explanation: The value specified in an IDENTIFY statement with the LEN or OCCURS option causes the size of the data block described by the current image to overflow the FSCB. The FSCB is a User Language work area that is used to hold a data block and its related image definitions.

    Response: Use the VIEW LFSCB command to determine the current size of the FSCB. Use the UTABLE command to increase the value of the LFSCB parameter. Check the User Language request for programming errors that might cause the value specified in the IDENTIFY statement to be too large. Retry the request.

    Return Codes: C 0 4 CANCEL AUDITER

    M204.1589:
    Maximum IMAGE length is 32767: LFSCB required = num

    Explanation: An attempt has been made to define an image greater than 32K.

    Response: Redefine the image so that it is not greater than the maximum length of 32767.

    Return Codes: C 0 4 CANCEL AUDITER

    M204.1938:
    REQUEST FOR SPACE IN TABLE E EXTENDS BEYOND EHIGHPG, BIT MAP PAGES ARE SCANNED FOR FREESPACE

    Explanation: A User Language request attempted to store a large object and all of the append pages in Table E have been allocated. Model 204 must scan the bit map pages for previously allocated Table E pages to look for free space to store the large object.

    File manager response: The file should be reorganized to compact fragmented Table E space.

    Return Codes: I 0 0

    M204.2126:
    USER'S PUSHDOWN LIST OVERFLOWED
    Explanation: The user's pushdown list is an internal stack for maintaining state information for user threads across internal Model 204 subroutines. The user pushdown list lives in each user's server. Its size requirement depends on the complexity of the command or User Language request.

    This message is issued whenever Model 204 detects that pushdown list data has spilled into adjacent control structures. Because of potential corruption the user is restarted.
    Response: Increase the size of the user pushdown list by using the LPDLST parameter of the UTABLE command. Notify your system manager.
    System Manager Response: If this becomes a frequent occurrence, consider more permanent changes to LPDLST and SERVSIZE, since the pushdown list is a server component.
    Return Codes: C 0 4 CANCEL

    M204.2329:
    subsystem name AT location name UNAVAILABLE

    Explanation: The indicated subsystem at the specified node is not available for use due to one or more errors occurring at the specified node during start or login processing.

    Response: Notify the system manager or try again later.

    System manager response: If the subsystem is started, stop the subsystem and resolve communications errors or other errors which occurred at the specified node. After resolving error, use the START SUBSYSTEM command to make the subsystem available for general use. Check to make sure that the LOCATION parameter was set properly in the CCAIN input stream for the Online.

    Return Codes: C 0 4

    M204.2551:
    {FPL|FCT PG1} IS INVALID FOR FILE: filename
    Explanation: If the message says FPL, then the FPL (file parameter list) for the associated file is invalid. This could be the result of an incorrect DD, FILEDEF or DLBL statement.

    If the message says FCT PG1, then the existence page array page is invalid.

    File Manager Response: If the DD, FILEDEF or DLBL statement is correct and points to the correct data set, then the file must be restored from a backup.
    Return Codes: C 0 4 AUDITER

    M204.2651:
    NOT ALL THREADS PROCESSED FOR IODEV %C

    Explanation: The run is terminated because either:

    • The number of threads specified by NUSERS has been initialized, but there are fewer users of the specified IODEV type than expected.
    • The DUPTERM number specified by the IODEV card could not be initialized because it exceeded the number of NUSERS.

    Response: Check that NUSERS matches the total of the listed IODEVs, plus one extra for USER 0. Check also the NOTERM/DUPTERM parameter for the specified IODEV card.

    Return Codes: E 80 80 ER

    M204.2719:
    OPEN %C FAILED. UPDATE STATEMENTS ALREADY COMPILED, READ ONLY PRIVILEGES INSUFFICIENT

    Explanation: The OPEN or OPENC User Language statement was issued from a request to reopen a file with read-only privileges. However, that request had already been compiled with update statements against the file.

    Response: In a User Language request, you cannot use the User Language OPEN or OPENC statement to reopen a file with read-only privileges, if that request contains updates statements against the same file.

    Descriptor code: C 0 4 CANCEL

    M204.2739:
    PARAMETER parm CANNOT BE RESET ON USER 0’S PARAMETER LINE: VALUE IGNORED

    Explanation: You reset parameter parm on the User 0 parameter line, but the parameter cannot be set there. The value is ignored, the default value for this parameter remains in effect.

    Response: Remove parm from the User 0 parameters, since it will not change the value of the parameter.

    Descriptor code: E 0 4 AD

    M204.2746:
    XSIZE*XRECPPG MAY NOT BE 1 NOR EXCEED 536870911

    Explanation: The product of XSIZE and XRECPPG must not exceed 16777216 times 32 minus one, or 536870911. This specifies the maximum number of extension records allowed in a single Model 204 file when using Table X. Also, setting both XRECPPG and XSIZE to 1 is invalid.

    The CREATE command is rejected.

    Response: Retry the command specifying values for XSIZE and XRECPPG whose product does not exceed the 526870911 limit. Refer to the Rocket Model 204 File Manager’s Guide for more information on file sizes.

    Descriptor code: C 0 4

    M204.2826:
    %F VERSION IS PRE 6.3. COMPACTION NOT ALLOWED
    Explanation: An attempt was made to compact a file created prior to Model 204 version 6.3.
    File Manager Response: Reorganize the file using Model 204 version 6.3.
    Return Codes: C 0 4 AUDITER

    M204.2831:
    UPDATES TO DTS FILES NOT SUPPORTED IN THIS ENVIRONMENT

    Explanation: DTS files cannot be updated in IFAM, SQL, or PQO environments.

    Response: Do not attempt to update DTS file.

    Return Codes: C 0 4

    M204.2833:
    FIELDS CANNOT BE DEFINED IN A FILE WITH ATRPG*ASTRPPG>4000

    Return Codes: C 0 4

    M204.2836:
    VALUE OF PARAMETER %C INVALID—RESET TO %C
    Explanation: This is an informational message only.

    A parameter was specified with an incorrect value. It has been reset to an internally calculated value that will accommodate other parameter settings. See the description of the parameter named to see what that calculation involves.
    System Manager Response: The parameter has been reset. No response required.
    Return Codes: I 0 0 AUDITMS

    M204.2838:
    %C ONLY VALID IN FILEORG X’100’ FILES

    Return Codes: C 0 4

    M204.2839:
    %C IS A %C, NOT A %C

    Return Codes: C 0 4 ECHO

    M204.2841:
    REMOTE FIELDGROUPS NOT SUPPORTED

    Return Codes: C 0 4 ECHO

    M204.2842:
    INVALID CONTEXT FOR FIELDGROUP

    Return Codes: C 0 4 ECHO

    M204.2843:
    MAXIMUM FIELDGROUP ID EXCEEDED IN RECORD %R IN %F

    Return Codes: C 0 4 CANCEL

    M204.2844:
    MIX OF FIELDS AND FIELDGROUPS, NAME =

    Return Codes: C 0 4 SUFFIX ECHO

    M204.2845:
    INVALID FIELDGROUP CONTEXT FOR %C

    Explanation: The $function was used outside of field group context.

    Descriptor code:C 0 4 SUFFIX ECHO

    M204.2846:
    INVALID FIELDGROUP CONTEXT FOR %C

    Return Codes: C 0 4 CANCEL

    M204.2847:
    FIELDGROUP CONTEXT LOST IN RECORD %R IN %F

    Return Codes: C 0 4 CANCEL

    M204.2848: INVALID FIELDGROUP ID: %C

    Return Codes: C 0 4 CANCEL

    M204.2849: REQUIRED KEYWORD %C MISSING

    Return Codes: X 0 4 ECHO

    M204.2850:
    %C VALUE MISSING

    Return Codes: C 0 4

    M204.2851:
    %C VALUE "%C" TOO BIG, MUST BE <%C BYTES

    Return Codes: C 0 4

    2852: UPDATE TO MISSING FIELDGROUP OCCURRENCE IN RECORD %R IN %F

    Return Codes: C 0 4 CANCEL

    2853: %C NOT ALLOWED FOR EXACTLY-ONE FIELD

    Return Codes: C 0 4

    2854: ATTEMPT TO DO %C FOR EXACTLY-ONE FIELD: %C

    Return Codes: C 0 4 CANCEL

    2855: FIELD DEPTH+LENGTH UNREPRESENTABLE IN RECORD %R IN %F

    Return Codes: C 0 4 CANCEL

    2856: FIELDNAME VARIABLE %C: EXPECTED %C, GOT %C

    Return Codes: C 0 4 CANCEL

    2857: %C FIELD NOT ALLOWED FOR %C FIELD

    Return Codes: C 0 4

    2858: FIELDGROUP CONTEXT MISMATCH BETWEEN COUNTOCCURRENCES- OF FIELD AND COUNTED FIELD

    Return Codes: C 0 4

    2859: NEW AUTOMATIC FIELD NOT ALLOWED FOR NON-EMPTY FILE

    Return Codes: C 0 4

    2860: FIELD %C ALREADY HAS A COUNT-OCCURRENCES-OF FIELD

    Return Codes: C 0 4

    2861: OCCURRENCE COUNTER %C OVERFLOWED

    Return Codes: C 0 4 CANCEL

    2862: ATTEMPT TO UPDATE AUTOMATIC FIELD %C

    Return Codes: C 0 4 SUFFIX ECHO

    2863: ATTEMPT TO DO %C FOR AUTOMATIC FIELD: %C

    Return Codes: C 0 4 CANCEL

    2865:CANCELATTEMPT TO %C INVALID DATETIME VALUE: %C = %C'

    Return Codes: C 0 4 CANCEL

    2866: FILE ALREADY HAS %C FIELD

    Return Codes: C 0 4

    2867: FIELDGROUP %C ALREADY HAS %C FIELD

    Explanation: If you try to define a second update tracker field of the same type for the same field group, you will invoke message 2867, where %C represents:

    • A CREATE-TIME
    • A CREATE-TIMEUTC
    • A CREATE-USER
    • AN UPDATE-TIME
    • AN UPDATE-TIMEUTC
    • AN UPDATE-USER

    Return Codes: C O 4

    2868: MINLOBE MUST BE BETWEEN 0 AND %C'

    Return Codes: C 0 4

    M204.2869:
    CHANGE REFUSED: MINLOBE > 0 FOR %F FIELD %C
    Return Codes: C 0 4 AUDITER

    M204.2870:
    CHANGE REFUSED: MINLOBE > 0 FOR %F FIELD %C
    Return Codes: C 0 4 CANCEL AUDITER

    2871: FIELDGROUP CONTEXT MISMATCH BETWEEN CONCATENATION-OF FIELD AND COMPONENT FIELD'

    Return Codes: C 0 4

    2872: CONCATENATION VALUE TOO LONG FOR FIELD %C'

    Return Codes: C 0 4 CANCEL

    2873: CONCATENATION FIELD %C COMPONENT FIELD %C CONTAINS SEPARATOR CHARACTER'

    Return Codes: C 0 4 CANCEL

    2874: ATTEMPT TO %C A VALUE THAT'S %C: %C

    Return Codes: C 0 4 CANCEL

    2875: CONCATENATION LIST INVALID: %C'

    Return Codes: C 0 4

    2876: INVALID %C VALUE: %C'

    Return Codes: C 0 4

    2877: WITH CLAUSE INVALID: %C'

    Return Codes: C 0 4 ECHO

    2878: WITH CLAUSE INVALID: FIELD %C IN %F %C

    Return Codes: C 0 4 CANCEL

    2879: REMOTE ID %C MODE %C'

    Return Codes: I 0 0 SAVE NOTERM OPR

    2880: MEMORY DATASETS CANNOT BE PART OF MULTI-DATASET FILE

    Return Codes: C 0 4

    2881: DATA CONVERSION ERROR

    Return Codes: C 0 4 CANCEL

    2882: RECOVERY JOURNAL VERSION %X IS NOT SUPPORTED

    Return Codes:E 0 4 OPR

    2884: [FIELD | FIELDGROUP] WAS PREVIOUSLY DEFINED AS A [FIELDGROUP | FIELD], NEW DEFINITION IGNORED

    Return Codes: C 0 4

    2885: INVALID FIELDGROUP ID: fieldgroup

    Return Codes: C 0 4 CANCEL

    2886: FIELDGROUP ID %C ALREADY EXISTS IN RECORD %R IN %F'

    Return Codes: C 0 4

    2903: FILEORG=X'100' IS NOT SUPPORTED DURING FLOD/FILELOAD

    Return Codes: E 0 8

    M204.2933:
    'Module version mismatch, KOMM=%C, %C=% C'
    Return Codes: E 0 4 SNAP

    M204.2934:
    FILEORG X''200'' not supported for hashed or sorted file organizations
    Explanation: Hashed or sorted files must be 16M files. The CREATE FILE command is rejected.
    File Manager Response: Remove the conflicting FILEORG parameter and reissue CREATE FILE.
    Return Codes: E 0 4 AUDITMS

    M204.2935:
    {CHUNK|CHUNK target} FIELDS MAY NOT BE RENAMED OR DELETED

    File Manager Response: Do not attempt to RENAME or DELETE chunks or chunk targets.
    Return Codes: C 0 4 AUDITER

    M204.2936:
    A CHUNK FIELD OF SIZE nnn ALREADY EXISTS FOR THIS FIELD
    Explanation: For a given CHUNK target field, duplicate chunk sizes are not permitted.
    File Manager Response: Correct the DEFINE FIELD that caused the message.
    Return Codes: C 0 4 AUDITER

    M204.2937:
    CHUNK SIZE: nnn IS NOT AN INTEGRAL MULTIPLE/DIVISOR OF THE EXISTING CHUNK SIZE: nnn
    Explanation: A CHUNK field's chunk size must be an integral multiple/divisor of all other chunk's sizes for a given chunk target.
    This message identifies the existing chunk size that conflicts with the new one.
    File Manager Response: Correct the DEFINE FIELD that caused the message.
    Return Codes: C 0 4 AUDITER

    M204.2938:
    YOU MAY NOT DEFINE MORE THAN 20 CHUNKS FOR A FIELD
    Explanation: A given chunk target can have at most 20 chunks defined.
    File Manager Response: Do not try to define more than 20 CHUNK fields for any given CHUNK target field.
    Return Codes: C 0 4 AUDITER

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_Model_204_version_7.5&oldid=64794"