## SRTCOPY

Destination: USER-TASK Routing code: Weight:

Warranty : NO

SRTCOPY Copyright (C) (&01'2014') (&00'Fujitsu Technology Solutions GmbH') ALL RIGHTS RESERVED

## SRTLOAD

Destination: USER-TASK Routing code: Weight:

Warranty : NO

SRTLOAD Program 'SORT', Version '08.0A' of '2018-04-11' loaded

## SRTSTRT

Destination: USER-TASK Routing code: Weight:

Warranty : NO

SRTSTRT Program 'SORT', Version '08.0A' of '2018-04-11' started

## SRT1001

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1001 (&00) (&01)/(&02) SORT/MERGE STARTED, VERSION (&03)

### Meaning

The time of day (&01) is the starting point for calculating the runtime,
i.e. the difference between the times in SRT1001 and SRT1002.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss)
(&03): SORT version/BS2000 version (nn.nAnn/BS2000Vnn.n).
Message weight: 3.

## SRT1002

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1002 (&00) (&01)/(&02) SORT/MERGE COMPLETED

### Meaning

The sort/merge routine terminated normally.
The time of day (&01) permits calculation of the total runtime, i.e. of
the difference between the time specifications in SRT1001 and SRT1002.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time for the entire sort/merge run (ssssss.ss).
Message weight: 2.

## SRT1003

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1003 (&00) (&01)/(&02) INTERRUPT IN (&03) PHASE

### Meaning

The sort/merge run was interrupted using the interrupt key.
The interrupt exit INT was activated by a subsequent /SEND-MSG command.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss)
(&03): phase in which SORT was interrupted.
Possible values:
CONTROL : Control
DECODING : Decoding
REVIEW : Review
PLANNING : Planning
PRESORT : Presort
DOMINO : Domino sort
PREMERGE : Internal merge
ENDMERGE : Final merge
EX-MERGE : External merge.
Message weight: 3.

### Response

A subsequent message indicates the appropriate response.

## SRT1004

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1004 (&00) PLEASE ENTER RESPONSE: (TERMINATE;CONTINUE(&01)

### Meaning

Only the responses listed in the message text are allowed in the present
situation.
(&00): prefix
(&01): other permissible responses.
Message weight: 3.

### Response

TERMINATE: Terminate processing
CONTINUE : Continue processing
If listed in the message text:
DISPLAY : Display sequence status (current counter)
FINISH : Stop input - process records that have been input
CKPT : Take a checkpoint at the next opportunity
START : Restarting SORT.
The responses can be abbreviated as long as they remain unambiguous.

## SRT1005

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1005 (&00) ILLEGAL RESPONSE

### Meaning

An illegal response was given to message SRT1004.
Subsequent to this message the message SRT1004 is repeated. Only the
responses displayed in the message text of SRT1004 are allowed in the
current situation.
(&00): prefix.
Message weight: 3.

### Response

Input the correct response after SRT1004.

## SRT1006

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1006 (&00) (&01)/(&02) EXIT E01: STATEMENT CHECK COMPLETED

### Meaning

User exit E01 was specified in the MODS statement. The sort/merge routine
reports that all statements have been decoded and checked.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss).
Message weight: 3.

## SRT1007

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1007 (&00) (&01)/(&02) EXIT E02: VALIDITY CHECK AND GENERATION COMPLETED

### Meaning

User exit E02 was specified in the MODS statement. SORT reports that all
validity checks and generation work have been completed.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss).
Message weight: 3.

## SRT1008

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1008 (&00) (&01)/(&02) EXIT (&03): END OF PLANNING PHASE

### Meaning

User exit PLANNING or E03 was specified in the ASSIGN-EXITS or MODS
statement.
By means of messages SRT1031 and SRT1033, SORT reports that the planning
phase has been completed.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss)
(&03): User exit PLANNING or E03.
Message weight: 3.

## SRT1009

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1009 (&00) EXIT (&01): PRIMARY DISK WORK AREA NEARLY EXHAUSTED

### Meaning

User exit WORK-FILE-OVERFLOW or E32 was specified in the ASSIGN-EXITS
or MODS statement. The sort/merge routine reports that the primary disk
work area is nearly exhausted. Abortion of the sort run is imminent.
(&00): prefix
(&01): User exit WORK-FILE-OVERFLOW or E32.
Message weight: 3.

## SRT1010

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1010 (&00) (&01)/(&02) END OF PRESORT PHASE

### Meaning

If sorting runs in cycles, this message appears with each cycle.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss).
Message weight: 0.

## SRT1011

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1011 (&00) (&01)/(&02) END OF INTERNAL MERGE

### Meaning

If sorting runs in cycles, this message appears with each cycle.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss).
Message weight: 0.

## SRT1012

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1012 (&00) NO INTERNAL MERGE NECESSARY

### Meaning

Only presorting and final merging is performed.
(&00): prefix.
Message weight: 0.

## SRT1013

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1013 (&00) MAIN MEMORY SORT

### Meaning

SORT reports that sorting is restricted to main memory and that no work
file is required.
(&00): prefix.
Message weight: 0.

## SRT1014

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1014 (&00) (&01)/(&02) SORT SUBTASK STARTED, VERSION (&03)

### Meaning

During multitask sorting, a subtask for internal sorting of a cycle
section has been started. The message appears in two places only, i.e.
in the SET-SORT-OPTIONS or OPTION statement if MIN-MSG-WEIGHT=ALL or MSG=0
is specified, or in the subtask log. In the case of another message
priority, the entire message log is suppressed.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss)
(&03): SORT version (n.nAnn).
Message weight: 0.

## SRT1015

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1015 (&00) (&01)/(&02) END OF CYCLE (&03)

### Meaning

SORT reports the end of cycle (&03) during cycle sorting.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss)
(&03): cycle number.
Message weight: 0.

## SRT1016

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1016 (&00) SORT/MERGE INPUT RECORDS:........(&01) (FROM (&02))

### Meaning

(&01) records were read in from the input file SORTINxx/MERGExx.
Records bypassed due to a INPUT-RANGE or SKIP operand are not included.
(&00): prefix
(&01): number of records that were input
(&02): file link name (SORTINxx/MERGExx) of the input file.
Message weight: 2.

## SRT1017

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1017 (&00) RECORDS TO BE SORTED/MERGED:.....(&01)

### Meaning

(&01) records have been transferred for sorting/merging, whereby the
records inserted and omitted through user interface INPUT or E15/E21, or
through the SELECT-INPUT-RECORDS or INCLUDE/OMIT statement have already
been taken into account. This message is only issued if the number of
records (&01) differs from that specified in message SRT1016 or if several
input files have been processed.
(&00): prefix
(&01): number of records to be sorted.
Message weight: 2.

## SRT1018

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1018 (&00) INSERTED INPUT RECORDS:..........(&01)

### Meaning

SORT reports at the end of the sort/merge run that (&01) records
were inserted via user exit INPUT or E15/E21.
(&00): prefix
(&01): number of inserted input records.
Message weight: 2.

## SRT1019

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1019 (&00) DELETED INPUT RECORDS:...........(&01)

### Meaning

SORT reports at the end of the sort/merge run that (&01) records were
deleted via user exit INPUT or E15/E21.
(&00): prefix
(&01): number of deleted input records.
Message weight: 2.

## SRT1020

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1020 (&00) DELETED SUM RECORDS:.............(&01)

### Meaning

At the end of the sort/merge run, SORT reports that (&01) records were
totalled and deleted due to the SUM-RECORDS or SUM statement.
(&00): prefix
(&01): number of deleted sum records.
Message weight: 2.

## SRT1021

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1021 (&00) SORTED/MERGED RECORDS:...........(&01)

### Meaning

SORT reports that (&01) records were sorted or merged.
The specified number was counted before user exit OUTPUT or E35/E23 was
reached and is therefore not to be equated with the number
of output records. This message is only issued if (&01) is not equal to
the number of records specified in message SRT1030.
(&00): prefix
(&01): number of sorted or merged records.
Message weight: 2.

## SRT1022

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1022 (&00) INSERTED OUTPUT RECORDS:.........(&01)

### Meaning

At the end of the sort/merge run, SORT reports that (&01) records
were inserted via user exit OUTPUT or E35/E23.
(&00): prefix
(&01): number of inserted output records.
Message weight: 2.

## SRT1023

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1023 (&00) DELETED OUTPUT RECORDS:..........(&01)

### Meaning

At the end of the sort/merge run, SORT reports that (&01) records
were deleted via user exit OUTPUT or E35/E23.
(&00): prefix
(&01): number of deleted output records.
Message weight: 2.

## SRT1024

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1024 (&00) DELETED (&02) RECORDS:....(&01)

### Meaning

At the end of the sort/merge run, SORT reports that (&01) records were
not included in the sort/merge operation due to specifications in the
SELECT-INPUT-RECORDS or INCLUDE/OMIT statement.
(&00): prefix
(&01): number of deleted records
(&02): SELECT-INPUT-RECORDS or INCLUDE/OMIT statement.
Message weight: 2.

## SRT1025

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1025 (&00) PAM INPUTS:......................(&01)

### Meaning

SORT required (&01) input blocks, i.e. chained PAM pages, from work files.
(&00): prefix
(&01): number of input blocks, i.e. chained PAM pages.
Message weight: 0.

## SRT1026

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1026 (&00) PAM OUTPUTS:.....................(&01)

### Meaning

SORT reports that (&01) output blocks, i.e. chained PAM pages, were output
to work files.
(&00): prefix
(&01): number of output blocks, i.e. chained PAM pages.
Message weight: 0.

## SRT1027

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1027 (&00) STRINGS AFTER PRESORTING:........(&01)

### Meaning

During presorting, (&01) strings (i.e. sorted record sequences) were
created.
(&00): prefix
(&01): number of strings.
Message weight: 1.

## SRT1028

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1028 (&00) STRINGS AFTER DOMINO:............(&01)

### Meaning

Using the DOMINO procedure, (&01) new, reorganized strings were created
out of the presort strings.
(&00): prefix
(&01): number of strings (sorted record sequences).
Message weight: 1.

## SRT1029

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1029 (&00) CYCLE OUTPUT RECORDS:........................(&01)

### Meaning

SORT reports that the subtask has sorted (&01) records in a multitask
sort.
This message only occurs if MIN-MSG-WEIGHT=ALL or MSG=0/1 is specified in
the SET-SORT-OPTION or OPTION statement and only appears in the subtask
log.
(&00): prefix
(&01): number of cycle output records.
Message weight: 1.

## SRT1030

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1030 (&00) SORT/MERGE OUTPUT RECORDS:.......(&01)

### Meaning

At the end of the sort/merge run, SORT reports that (&01) records
were written to the output file (SORTOUT).
(&00): prefix
(&01): number of output records.
Message weight: 2.

## SRT1031

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1031 (&00) ESTIMATED WORK FILE PAM PAGES:...(&01)

### Meaning

User exit PLANNING or E03 was specified in the ASSIGN-EXITS or MODS
statement. The sort/merge routine reports that, on the basis of the
available data (e.g. DISK-SPACE or DM in the ASSIGN-RESOURCES or ALLOC
statement), (&01) PAM pages have been calculated as necessary for the
work file.
(&00): prefix
(&01): number of PAM pages for the work file.
Message weight: 3.

## SRT1032

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1032 (&00) *** OVERFLOW. IGNORED SAME SORT KEY RECORDS:.....(&01) ***

### Meaning

A SUM-RECORDS or SUM statement was specified for this sort run.
SORT reports that not all records with the same sort key could be
totalled as this would lead to an overflow.
Once sorting has been completed, the run is terminated with an error.
(&00): prefix
(&01): number of records with the same sort key which could not be
totalled.
Message weight: 3.

### Response

If the user desires complete compression, a field extension must be
specified in the SUM-RECORDS or SUM statement for the sum field and the
sort run has to be repeated. This causes the record to be extended.
The output file produced by this sort run can be used as the input file
in the next sort run, thus helping to save time.

## SRT1033

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1033 (&00) FREQUENTLY USED CORE PAGES:......(&01)

### Meaning

User exit PLANNING or E03 was specified in the ASSIGN-EXITS
or MODS statement. SORT reports that (&01) memory pages have been
requested for intensive use.
(&00): prefix
(&01): number of memory pages for intensive use.
Message weight: 3.

## SRT1034

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1034 (&00) WARNING: NO INPUT RECORDS FOR SORT/MERGE

### Meaning

An empty input file was specified and/or no records were passed to SORT
via user exit INPUT or E15/E21 or all records were deleted by
SELECT-INPUT-RECORDS OR INCLUDE/OMIT statement.
The run is terminated normally.
(&00): prefix.
Message weight: 3.

### Response

Repeat the sort/merge run with the appropriate input specifications if
necessary.

## SRT1035

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1035 (&00) *** DMS ERROR '(&01)' DURING OPENING OF FILE '(&02)'. IN SYSTEM MODE: /HELP-MSG DMS(&01) ***

### Meaning

If the invalid file is an input file allocated by LINK=SORTINxx, the
sort/merge routine responds as specified in the INPUT-OPEN-ERROR
or INOPERR operand of the SET-SORT-OPTIONS or OPTION statement
(see the 'SORT (BS2000)' manual). If the invalid file is a scratch file
allocated by LINK=SORTWKxx, SORT bypasses it and continues with the next
scratch file. Open errors on other SORT files cause abortion of the run.
For more detailed information about the DMS error code enter /HELP-MSG.
(&00): prefix
(&01): DMS error code
(&02): file link name.
Message weight: 3.

### Response

In the case of errors when opening files assigned by SORTINxx, SORT
requests input of a response in interactive mode by issuing message
SRT1004, if the operand INPUT-OPEN-ERROR or INOPERR is not specified in
the SET-SORT-OPTIONS or OPTION statement.

## SRT1036

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1036 (&00) *** DMS ERROR '(&01)' ON FILE '(&02)'. IN SYSTEM MODE: /HELP-MSG DMS(&01) ***

### Meaning

During processing of file (&02), the sort/merge routine detected
an unrecoverable DMS error.
For more detailed information about the DMS error code enter /HELP-MSG.
If at least one of the status bytes SDB, OSB or EXFB is not equal to zero,
message SRT1037 is issued.
(&00): prefix
(&01): DMS error code
(&02): file link name.
Message weight: 3.

## SRT1037

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1037 (&00) STATUS BYTES: SDB=(&01); OSB=(&02); EXFB=(&03)

### Meaning

This message follows SRT1036 and provides information on
standard device byte SDB, sense byte OSB and flag byte EXFB.
The run is aborted.
(&00): prefix
(&01): Standard device byte SDB
(&02): Sense byte OSB
(&03): Flag byte EXFB.
Message weight: 3.

## SRT1038

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1038 (&00) (&01)/(&02) *** SORT/MERGE ABORTED ***

### Meaning

When SORT is called as a subroutine, register 15 contains
- the error flag X'FF' (right-justified) and
- the last 4 digits of the message code (left-justified).
These describe the error.
If SORT is running autonomously, it aborts with
TERM MODE=ABNORMAL,UNIT=STEP.
Also a subprogram can be aborted with TERM in some exceptional cases.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss:)
(&02): CPU time (ssssss.ss).
Message weight: 3.

### Response

Investigate the cause of abnormal termination and repeat the sort run
or the main program after eliminating the error.

## SRT1039

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1039 (&00) *** INTERNAL SORT ERROR X'(&01)' AT PROGRAM COUNTER X'(&02)' ***

### Meaning

An internal sort/merge error with error code X'(&01)' was found at
program counter X'(&02)'.
SORT issues the message SRT1041, which initiates the output of a special
SORT dump and a general user dump.
(&00): prefix
(&01): error code (event code)
(&02): Program counter.
Message weight: 7.

## SRT1040

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1040 (&00) *** SORT/MERGE OUTPUT OUT OF SEQUENCE ***

### Meaning

- In sort runs this error is normally treated like an internal error
(see message SRT1039). With message SRT1041 issued subsequent to this
message the output of the special SORT dump and the general user dump
is requested by SORT.
In case of exit EXTERNAL-COMPARE or EXA/EXT or OUTPUT or E23/E35 the
program reacts like in a merge run.
- In merge runs it can usually be traced to a previous sequence error in
the input file. This user error is explained by a dump output to SYSLST
containing the last correct and the first invalid input record.
Furthermore, in interactive mode up to 8 dump lines of each record are
displayed on the screen.
(&00): prefix.
Message weight: 3.

### Response

In the case of merge runs, check that input files are in the correct
sequence and, if necessary, sort accordingly. If no sequence checking
is requested, the operand SEQUENCE-CHECK=NO or SEQ=NO must be
specified in the SET-SORT-OPTIONS or OPTION statement.
Then restart the run.

## SRT1041

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1041 (&00) *** PLEASE PRINT SORT DUMP WITH 'SODUMP' OR 'DAMP' AND SEND IT TO SYSTEMS ENGINEER ***

### Meaning

An unrecoverable error occurred during the sort/merge run.
A user dump and a special SORT dump are generated.
SORT is then aborted.
(&00): prefix.
Message weight: 3.

### Response

Print out the user dump using the SODUMP or DAMP utility routine and
send it to the systems engineer together with the special SORT dump
output to SYSLST.

## SRT1042

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1042 (&00) (&01)/(&02) WARNING: CHECKPOINT CANNOT BE SET DUE TO OUTPUT ERROR; ERROR CODE=X'(&03)'

### Meaning

The sort/merge routine reports that a checkpoint could not be
set because of the error identified by (&03).
The sort/merge run continues normally.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss)
(&03): error code of the WRCPT macro (see the 'Executive Macros' manual)
Message weight: 3.

### Response

Check and contact the system administrator if necessary.

## SRT1043

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1043 (&00) *** INSUFFICIENT VIRTUAL ADDRESS SPACE. RUN IS ABORTED ***

### Meaning

Error when requesting class 6 memory.
(&00): prefix.
Message weight: 3.

### Response

Find out why there is not enough virtual address space and, if necessary,
contact the system administrator.
Repeat the sort/merge run after remedying the storage deficiency.

## SRT1044

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1044 (&00) *** WORK FILE/SCRATCH FILE CANNOT BE EXTENDED. RUN IS ABORTED ***

### Meaning

The memory space for work files/last scratch file has been used up.
No more space can be requested because
- 0 was specified as the size of secondary storage
- there is no more free space on public or private disk
- erroneously a tape was assigned as work file
(&00): prefix.
Message weight: 7.

### Response

- Calculate the memory space correctly or
- Use the operand ESTIMATED-RECORDS or SIZE of the SORT-RECORDS or SORT
statement to specify the number of records and leave the rest to the
sort/merge routine
- assign work file on disc
Afterwards repeat the run.

## SRT1045

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1045 (&00) SORT/MERGE RUN ABORTED BY USER ROUTINE

### Meaning

The sort or merge run was aborted by a user routine using the
return code X'10'.
(&00): prefix.
Message weight: 1.

## SRT1046

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1046 (&00) (&01)/(&02) END OF PREPARATORY PHASE

### Meaning

The sort or merge routine reports that the preparatory phase
(decoding, validity checking and generation) has been completed.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh.mm.ss)
(&02): CPU time (ssssss.ss) used.
Message weight: 0.

## SRT1047

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1047 (&00) *** DATA ERROR X'(&01)' AT PROGRAM COUNTER X'(&02)' ***

### Meaning

The error occurred during a sort field match, a summation of records or a
conversion. SORT initiates a user dump.
(&00): prefix
(&01): Data error code (interrupt weight)
(&02): Program counter.
Message weight: 7.

### Response

Check the statements and input data.
If necessary, contact the system administrator.

## SRT1048

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1048 (&00) *** ERROR X'(&01)' IN USER ROUTINE '(&03)' AT PROGRAM COUNTER X'(&02)' ***

### Meaning

The subsequent message SRT1049 provides information about the start
address of the invalid user routine.
If the command /SET-SORT-OPTIONS DUMP=YES is given the user dump is taken
automatically.
(&00): prefix
(&01): error code (interrupt weight)
(&02): Program counter
(&03): Designation of the user exit.
Message weight: 7.

### Response

Take user dump if necessary.
Correct the user routine and then repeat the run.

## SRT1049

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1049 (&00) *** START ADDRESS OF USER ROUTINE: X'(&01)' ***

### Meaning

Message SRT1048 reported an error in a user routine. A user dump is
initiated subsequent to this message.
(&00): prefix
(&01): Start address of the user routine.
Message weight: 3.

### Response

Correct the user routine and then repeat the run.

## SRT1050

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1050 (&00) BLOCK SIZE IN PAM PAGES:.........(&01)

### Meaning

The sort/merge routine reports the internal block size of the work and
scratch files.
(&00): prefix
(&01): Block size in PAM pages.
Message weight: 1.

## SRT1051

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1051 (&00) *** SORT SUBTASK '(&01)' ABORTED ***

### Meaning

(&00): prefix
(&01): number of the subtask.
Message weight: 3.

### Response

The records specified as missing in messages SRT1052 and SRT1053
can be postsorted using an appropriate INPUT-RANGE or SKIP
specification in the SORT-RECORDS or SORT statement and then merged into
the records already sorted.

## SRT1052

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1052 (&00) SUBTASK BEGAN AFTER RECORD:..................(&01)

### Meaning

The aborted subtask started after record (&01) of the sort run.
(&00): prefix
(&01): number of record after that the aborted subtask began.
Message weight: 3.

### Response

In conjunction with the following message SRT1053, the record range of a
supplementary sort run is specified via the INPUT-RANGE or SKIP operand
of the SORT-RECORDS or SORT statement.

## SRT1053

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1053 (&00) LOST RECORDS IN SUBTASK:.....................(&01)

### Meaning

(&01) records have been lost in the aborted subtask.
(&00): prefix
(&01): number of lost records.
Message weight: 3.

### Response

The records specified as lost in messages SRT1052 and SRT1053 can be
postsorted using an appropriate INPUT-RANGE or SKIP operand from the
SORT-RECORDS or SORT statement and then merged into the records already
sorted. If insertions/deletions were made via user exit INPUT or E15/E21,
the number of records lost will no longer correspond to the value for
NUMBER-OF-RECORDS or 'value2' in the INPUT-RANGE or SKIP operand.

## SRT1054

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1054 (&00) *** WARNING : RECORDS TRUNCATED AT MAX. RECORD LENGTH:......(&01) ***

### Meaning

Due to modifications to the record length, SORT has truncated (&01)
variable-length records to reduce them to the maximum record length.
(&00): prefix
(&01): number of records truncated.
Message weight: 3.

## SRT1055

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1055 (&00) WARNING: SORT COULD NOT SET A CHECKPOINT

### Meaning

There was no or insufficient storage space for the checkpoint file.
The sort/merge routine continues without writing a checkpoint.
If writing of the checkpoint was initiated via CKPT/TERMINATE,
TERMINATE is ignored.
(&00): prefix.
Message weight: 3.

## SRT1056

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1056 (&00) *** USER EXIT '(&01)' WITH BIND ERROR X'(&02)'. RUN IS ABORTED ***

### Meaning

A BIND error occurred while reloading the user routine for user exit
(&01).
(&00): prefix
(&01): user exit
(&02): error code of the BIND macro.
Message weight: 3.

### Response

Check whether the specified user routine is present in the module library
assigned via the link name SORTMODS or via link name BLSLIBxx.

## SRT1057

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1057 (&00) *** OBJECT MODULE '(&01)' WITH BIND ERROR X'(&02)'. RUN IS ABORTED ***

### Meaning

A BIND error occurred when dynamically loading object module (&01).
(&00): prefix
(&01): SORT object module name
(&02): error code of the BIND macro.
Message weight: 3.

### Response

Check the module library.

## SRT1058

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1058 (&00) WARNING: ERROR IN OUTPUT OF MESSAGE SRT(&01)

### Meaning

The sort/merge run continues.
(&00): prefix
(&01): number of the SORT message.
Message weight: 7.

### Response

Check whether this message exists in the system message file using
/HELP-MSG SRT(&01) or /HELP SRT(&01).
Contact the system administrator, if necessary.

## SRT1059

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

SRT1059 (&00) (&01)/(&02) *** SORT/MERGE TERMINATED WITH ERROR ***

### Meaning

An error occurred during the sort/merge run, without causing the run
to be aborted.
Possible reason:
- When sorting more than one file, SORT bypasses an input file with an
open error (see message SRT1035) when the operand
INPUT-OPEN-ERROR=CONTINUE-NEXT-FILE or
INPUT-OPEN-ERROR=TERMINATION=ABNORMAL is specified in the
SET-SORT-OPTIONS statement or
INOPERR=CONTJ is specified in the OPTION statement.
- Not all records with the same key could be totalled because
of an overflow (SUM-RECORDS or SUM statement).
- During multiple task sorting, SORT subtasks were aborted.
When SORT is called as a subroutine, register 15 contains the error flag
X'FF' (right-justified) and the last 4 digits of the message code of the
message describing the error (left-justified). When SORT is called as an
autonomous routine, the sort run is terminated with
TERM MODE=ABNORMAL,UNIT=STEP.
(&00): prefix
(&01): date/time of day (yyyy-mm-dd/hh:mm:ss)
(&02): CPU time (ssssss.ss).
Message weight: 3.

### Response

Check the console log and the input file.

## SRT1060

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1060 (&00) WARNING: SPACE ALLOCATION=((&01),0) TOO SMALL FOR SCRATCH FILE '(&02)'

### Meaning

SPACE=((&01),0) is too small for the scratch file. The run continues
with the following scratch file, which may increase the number of records
in the last cycle.
(&00): prefix
(&01): Primary space allocated to the scratch file
(&02): Link name of the scratch file.
Message weight: 3.

## SRT1061

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1061 (&00) MAXIMUM NUMBER OF MERGE PATHS:...(&01)

### Meaning

(&00): prefix
(&01): Maximum number of merge paths for final merge output
(in the case of an internal merge run, this number is reduced by
2).
Message weight: 1.

## SRT1062

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1062 (&00) VIRTUAL MERGE POSSIBLE

### Meaning

The CORE size specified in the ASSIGN-RESOURCES or ALLOC statement enables
virtual merging.
(&00): prefix.
Message weight: 1.

## SRT1063

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1063 (&00) END OF VIRTUAL MERGE (&01)

### Meaning

(&00): prefix
(&01): number of the virtual merge run.
Message weight: 0.

## SRT1064

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1064 (&00) *** SORT MODUL VERSIONS NOT EQUAL. RUN IS ABORTED ***

### Meaning

The prelinked modules SORTKERN or SRTXKERN and SORTGEN or SRTXGEN,
dynamically loaded by SORT, have different version numbers.
Possible reason:
SORTKERN or SRTXKERN is loaded with the 'share' attribute or as a
subsystem, and SORTGEN or SRTXGEN is dynamically loaded from a module
library belonging to another SORT version.
(&00): prefix.
Message weight: 3.

### Response

Ask the system administrator to load SORTKERN or SRTXKERN with the 'share'
attribute or SORT as a subsystem from the current module library.

## SRT1065

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1065 (&00) *** WARNING : EXPRESS ENTRY MISSING: MULTITASK SORTING NOT POSSIBLE. SWITCHING TO CYCLE SORTING ***

### Meaning

The user may not use the job express function. It is therefore not
possible to guarentee an immediate start for the subtask.
Multitask sorting is not possible.
Cycle sorting is used instead.
This could cause loss of performance.
(&00): prefix.
Message weight: 3.

### Response

Ask the system administrator to allow the job express function
(Command /MODIFY-USER-ATTRIBUTES with the parameter
' PRIVILEGE=*PARAMETERS(START-IMMEDIATE=*YES) ' in the section
'ACCOUNT-ATTRIBUTES' ).

## SRT1066

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1066 (&00) WARNING: EXPRESS ENTRY IS CHANGED. CYCLE SORTING IS PROCESSED

### Meaning

The EXPRESS entry was changed during sorting. The current and following
cycles are sorted by the main task. No more subtasks are started.
(&00): prefix.
Message weight: 3.

### Response

Please ask the system administrator to change the job express
function (Command /MODIFY-USER-ATTRIBUTES with the parameter
' PRIVILEGE=*PARAMETERS(START-IMMEDIATE=*YES) ' in the section
'ACCOUNT-ATTRIBUTES' ).

## SRT1067

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1067 (&00) *** SORT SUBTASK '(&01)' ABORTED OR NOT STARTED ***

### Meaning

The subtask (&01) did not report back to the main task.
(&00): prefix
(&01): current number of the subtask.
Message weight: 3

### Response

- Subtask was not started: determine the cause; abort subtask with
/CANCEL-TASK command.
- Subtask is aborted: determine the cause.
Remove the cause of error and repeat the run.
If necessary, compile error documents and send them to the systems
engineer.

## SRT1068

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1068 (&00) *** NO FREE WORK FILE AVAILABLE FOR NEXT CYCLE. RUN IS ABORTED ***

### Meaning

There is no free work file available for the next cycle in multitask
sorting;
all work files are occupied by subtasks started earlier.
The main task checks whether subtasks already started have reported a
successful start. If this does not happen immediately or within 10
minutes,
waiting for the end of the subtask is not appropriate.
In such a case, the run is aborted.
(&00): prefix.
Message weight: 3.

### Response

Detect and eliminate the cause of error (e.g. the subtask was put in
the wait state by the system).
Repeat the run.
If necessary, compile error documents and send them to the systems
engineer.

## SRT1069

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1069 (&00) INVALID RECORD COUNTER '(&01)'. RUN IS ABORTED

### Meaning

An inequality was discovered during checking of the record counter
according to formula (&01). Records were lost or added.
INPUT : A - B + C - D = E
INTERNAL: E - F - K = G
OUTPUT : G + H - I = J
A) records input by input file(s)
B) records deleted via SELECT-INPUT-RECORDS or INCLUDE/OMIT
C) records inserted via INPUT or E15/E21 exit
D) records deleted via INPUT or E15/E21 exit
E) records which are sent directly for sorting
F) records deleted via SUM-RECORDS or SUM
G) sorted records before output processing
H) records inserted via OUTPUT or E35/E23 exit
I) records deleted via OUTPUT or E35/E23 exit
J) records written to output file
K) lost records from SORT subtask runs
SORT produces an user dump.
(&00): prefix
(&01): concerned record counter.
Message weight: 3.

### Response

Send error documents to the systems engineer.

## SRT1070

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1070 (&00) WARNING: RECORDS FOUND WITH EQUAL ISAM KEY

### Meaning

The ISAM output file created (DUPLICATE-KEY=YES) contains records with
identical keys.
The following problems may result:
- It may not be possible to create secondary keys
(/CREATE-ALTERNATE-INDEX command).
- Access to records with the same key is ambiguous.
The run is terminated normally.
(&00): prefix.
Message weight: 2.

### Response

Extend the sort field or increase the key length in defined ISAM keys.
By specifying DUPLICATE-KEY=NO in /ADD-FILE-LINK, it is possible to abort
the sort run in the case of duplicated keys.

## SRT1071

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1071 (&00) *** INVALID ADDRESS X'(&01)' IN REGISTER (&02) WHEN CALLING SORT. RUN IS ABORTED ***

### Meaning

Accessing the address X'(&01)' causes an addressing error.
(&00): prefix
(&01): invalid address
(&02): name of the register.
Message weight: 3.

### Response

Correct invalid user program and repeat run.

## SRT1072

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1072 (&00) *** INVALID ADDRESS X'(&01)' OF A STATEMENT OR STATEMENT TABLE. RUN IS ABORTED ***

### Meaning

The address (&01) specified in the address list of the SORT input block
(SVB) is invalid. Accessing this address causes an error.
(&00): prefix
(&01): invalid address.
Message weight: 3.

### Response

Correct invalid user program and repeat run.

## SRT1073

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1073 (&00) *** INVALID ADDRESS X'(&01)' IN '(&02)' TABLE AT USER EXIT '(&03)'. RUN IS ABORTED ***

### Meaning

The user has provided the invalid address (&01) in the table (&02) for
a user routine in the user exit (&03).
Accessing this address results in an addressing error.
(&00): prefix
(&01): invalid address
(&02): ASSIGN-EXITS or MODS statement table
(&03): name of the user exit.
Message weight: 3.

### Response

Correct errored user program and repeat run.

## SRT1074

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1074 (&00) *** ADDRESS ERROR WHEN ACCESSING SVB. RUN IS ABORTED ***

### Meaning

The SVB created by the user is partly located in an invalid range. If
the SVB is created by the user, the most significant bit of the last
reference address specified in the SVB must be set to 1.
(&00): prefix.
Message weight: 3.

### Response

Correct errored user program and repeat run.

## SRT1075

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1075 (&00) *** INVALID ADDRESS X'(&01)' WHEN ACCESSING '(&02)' STATEMENT TABLE. RUN IS ABORTED ***

### Meaning

Possible reasons:
- An addressing error occurred when accessing the statement table since
part of the table is located in an invalid range.
- An incorrect table length was specified in variable tables.
(&00): prefix
(&01): invalid address
(&02): name of the statement table.
Message weight: 3.

### Response

Correct the errored user program and repeat the run.

## SRT1076

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1076 (&00) *** INVALID ADDRESS X'(&01)' WHEN ACCESSING RCF RANGE. RUN IS ABORTED ***

### Meaning

An addressing error occurred when accessing the RCF range.
(&00): prefix
(&01): invalid address.
Message weight: 3.

### Response

Check the specified address and the length of the RCF range.
Correct errors and repeat run.

## SRT1077

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1077 (&00) *** INVALID RECORD LENGTH FIELD X'(&01)' FOR STATEMENT. RUN IS ABORTED ***

### Meaning

An errored record length field X'(&01) was passed for a
statement when SORT was being set via level 1 (statements as
records of variable length in the memory). When accessing
this statement, an addressing error occurred.
(&00): prefix
(&01): errored record length.
Message weight: 3.

### Response

Correct errored user program and repeat run.

## SRT1078

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1078 (&00) *** INVALID RECORD ADDRESS X'(&02)' OR RECORD LENGTH X'(&03)' PASSED AT USER EXIT '(&01)'. RUN IS ABORTED ***

### Meaning

An addressing error occurred when accessing the record passed at
user exit '(&01)' (inserted or modified record).
(&00): prefix
(&01): name of the user exit
(&02): errored record address
(&03): errored record length field.
Message weight: 3.

### Response

Check the user routine of the user exit (&01) and correct errors.
Repeat the run.

## SRT1079

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1079 (&00) *** INVALID RECORD ADDRESS X'(&02)' OR RECORD LENGTH X'(&03)' PASSED WITH SZM MAKRO SRT(&01). RUN IS ABORTED ***

### Meaning

- Record passed with SZM macro SRTPUT:
An addressing error occurred when accessing the record. This
was caused by an invalid record address or record length.
- Record passed with SZM macro SRTGET:
An addressing error occurred when accessing the record. This
was caused by an invalid destination address or record length.
(&00): prefix
(&01): name of the macro (PUT, GET)
(&02): invalid record address/destination address
(&03): invalid record length field.
Message weight: 3.

### Response

Correct errored user program and repeat run.

## SRT1080

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1080 (&00) *** ADDRESS ERROR WHEN ACCESSING PARAMETER RANGE PASSED FROM USER EXIT '(&01)'. RUN IS ABORTED ***

### Meaning

Register 1 or the parameter range contains an invalid address.
(&00): prefix
(&01): name of the user exit.
Message weight: 3.

### Response

Check the user routine of the user exit (&01) and correct errors.
Repeat the run.

## SRT1081

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1081 (&00) *** NO EXLST MACRO PRESENT ON DISTANCE '0' OF THE USER ROUTINE '(&01)'. RUN IS ABORTED ***

### Meaning

If user exit (&01) is specified, there must be an EXLST macro on
distance '0' of the specified user routine.
(&00): prefix
(&01): name of the user exit.
Message weight: 3.

### Response

Check the user routine of the user exit (&01) and correct errors.
Repeat the run.

## SRT1082

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1082 (&00) FINAL MERGE: DOUBLE BUFFERING NOT POSSIBLE

### Meaning

The amount of storage space required by the main program is so great
that there is not enough space left over for double buffering.
For this reason, the last merge run (final merge) is carried out with
single buffering.
(&00): prefix.
Message weight: 0.

## SRT1083

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1083 (&00) *** ERROR WHEN INITIALIZING '(&01)' ENVIRONMENT. RUN IS ABORTED ***

### Meaning

For error reason see previous message.
(&00): prefix.
(&01): SPL or C.
Message weight: 3.

### Response

Investigate the error reason and repeat the SORT run
or the main program.

## SRT1084

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1084 (&00) *** CPU TIME EXCEEDED. RUN IS ABORTED ***

### Meaning

The CPU-Limit of the task has been exceeded.
(&00): prefix.
Message weight: 3.

### Response

Abortion in main task:
- increase value of CPU-LIMIT in the start command
- specify TIME=NTL in LOGON command
Abortion in subtask:
- assign job class with higher CPU-Limit
- use shorter sort cycles
repeat the run

## SRT1085

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1085 (&00) *** POSIX CALL '(&01)' ON FILE '(&02)': ERROR '(&03)' ***

### Meaning

All errors reported by POSIX-calls are output in this form.
The run is aborted.
(&00): Praefix.
(&01): Function which returns an error.
(&02): file link name
(&03): error code returned in C-variable errno.
For more detailed information about the error see the BS2000
manual 'C-library functions' or the BS2000 manual 'POSIX'.
Message weight: 3.

## SRT1086

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1086 (&00) *** WARNING: JOB CLASS '(&01)' FOR SUBTASK SET TO *STD ***

### Meaning

The attempt to start a subtask with JOB-CLASS (&01) was not successful.
JOB-CLASS was set to *STD.
Thereafter the start of the subtask was successful.
(&00): prefix.
(&01): requested JOB-CLASS.
Message weight: 3.

## SRT1087

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1087 (&00) *** SUBSYSTEM 'POSIX' NOT AVAILABLE IN SYSTEM. RUN IS ABORTED ***

### Meaning

POSIX must be started befor POSIX files can be processed by SORT.
(&00): prefix.
Message weight: 3.
PLEASE CORRECT RECORDS. END OF MEANING OF SRT1087 IN LANGUAGE E

### Response

Start POSIX subsystem. Repeat the run.
PLEASE CORRECT RECORDS. END OF REPLY OF SRT1087 IN LANGUAGE E

## SRT1088

Destination: USER-TASK Routing code: Weight:

Warranty : NO

SRT1088 (&00) ERROR IN FORMAT TWO-DIGIT-YEAR

### Meaning

The value for data field with TWO-DIGIT-YEAR must be in range between
0 and 99 (and not negative).
(&00): prefix.
Message weight: 3.

### Response

Correct data and repeat run.

## SRT1089

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1089 (&00) *** INVALID SORT TABLE FOR UNICODE. RUN IS ABORTED ***

### Meaning

The SORT table requested by XHCS-SYS is invalid.
Sort initiates a user dump.
(&00): prefix
Message weight: 3.

### Response

Inform the system administrator and correct the SORT table.
Repeat the run.

## SRT1090

Destination: USER-TASK Routing code: Weight:

Warranty : NO

SRT1090 MAXIMUM NUMBER OF RECORDS ISSUED

### Meaning

Only the maximum number of X'7FFFFFFF' = 2147483647 records can be
processed.
Processing is aborted.

## SRT1099

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1099 (&00) *** SORTLIB VERSION NOT EQUAL TO V8.0XXX ***

### Meaning

The called (linked) SORT start routine SRT80 with the version number
8.0xxx is not compatible with the current SORTLIB (older version).
(&00): prefix.
Message weight: 3.

### Response

Use a SORTLIB with the version number 8.0xxx and the associated
message file.

## SRT1101

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1101 (&00) (&01)

### Meaning

The sort/merge routine uses this message to output a section of an
invalid statement. In the following message SRT1102, the position
of the error is indicated by an exclamation mark (!).
(&00): prefix
(&01): Section of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1102

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1102 (&00) (&01)

### Meaning

The sort/merge routine indicates the position of the error in a section of
an invalid statement by means of an exclamation mark (!). The section was
identified by the previous message SRT1101.
(&00): prefix
(&01): Exclamation mark '!' for identifying the error position.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1103

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1103 (&00) SYNTAX ERROR IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following
messages SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement or 'CONTROL' for SDF
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1104

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1104 (&00) INVALID CONTINUATION CHARACTER IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following
messages SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1105

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1105 (&00) INVALID NUMERIC VALUE IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following
messages SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1106

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1106 (&00) DUPLICATE '(&01)' STATEMENT. LAST ENTERED STATEMENT IS VALID

### Meaning

- the last entered (&01) statement is valid.
(&00): prefix
(&01): name of the statement which has been entered more than once.
Message weight: 2.

### Response

Remove the superfluous statement.

## SRT1107

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1107 (&00) '(&01)' STATEMENT INVALID: DUPLICATED OPERAND

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1108

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1108 (&00) '(&01)' STATEMENT INVALID: A MAXIMUM OF 64 CONTROL FIELDS ARE PERMITTED

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1109

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1109 (&00) ERROR IN '(&01)' VALUE OF '(&02)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): invalid value
(&02): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1110

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1110 (&00) INVALID '(&01)' PREFIX IN '(&02)' STATEMENT

### Meaning

A mask or a constant was not properly specified (e.g. specification for
mask or constant type is not correct).
Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): type of invalid prefix
(CONST for constant prefix, MASK for mask prefix)
(&02): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1111

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1111 (&00) '(&01)' STATEMENT INVALID: CONSTANT LENGTH > (&02) BYTES

### Meaning

(&00): prefix
(&01): name of the invalid statement
(&02): maximum permissible value.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1112

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1112 (&00) HEXADECIMAL CONSTANT IN '(&01)' STATEMENT HAS ODD LENGTH

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1113

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1113 (&00) INVALID CHARACTER IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1114

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1114 (&00) DUPLICATE FIELD INFORMATION IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1115

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1115 (&00) INVALID SEQUENCE NUMBER IN '(&01)' STATEMENT

### Meaning

No more than 64 sort fields can be used.
Any sequence number greater than 64 is illegal.
Exact explanations for the error cause are given by the following
messages SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1116

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1116 (&00) INVALID SUBOPERAND '(&01)' IN '(&02)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid suboperand
(&02): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1117

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1117 (&00) INVALID OPERAND '(&01)' IN '(&02)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid operand
(&02): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1118

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1118 (&00) 'MODS' STATEMENT INVALID: MORE THAN 12 USER EXITS ARE DEFINED

### Meaning

(&00): prefix.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1119

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1119 (&00) 'MODS' STATEMENT INVALID: USER ROUTINE NAME > 8 CHARACTERS

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1120

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1120 (&00) ILLEGAL EXIT ACTION IN 'MODS' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1121

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1121 (&00) MORE THAN 64 SUM FIELDS IN '(&01)' STATEMENT

### Meaning

(&00): prefix
(&01): SUM-RECORDS or SUM statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1122

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1122 (&00) ILLEGAL SUM FIELD EXTENSION IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): SUM-RECORDS or SUM statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1123

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1123 (&00) MORE THAN 64 CONDITIONS IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): SELECT-INPUT-RECORDS or INCLUDE/OMIT statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1124

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1124 (&00) SUM OF LENGTHS OF ALL CONSTANT OR MASK FIELDS IN '(&01)' STATEMENT > (&02) BYTES

### Meaning

(&00): prefix
(&01): name of the invalid statement
(&02): maximum permissible value.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1125

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1125 (&00) INVALID HEXADECIMAL CONSTANT IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1126

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1126 (&00) MORE THAN 8 NESTED PAIRS OF PARENTHESES IN '(&01)' STATEMENT

### Meaning

Exact explanations for the error cause are given by the following messages
SRT1101 and SRT1102.
(&00): prefix
(&01): SELECT-INPUT-RECORDS or INCLUDE/OMIT statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1127

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1127 (&00) *** PROGRAM ERROR X'(&01)' IN MODULE '(&02)'. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): program error code
(&02): SORT module containing the error.
Message weight: 3.

### Response

Send details of the error to the systems engineer.

## SRT1128

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1128 (&00) (&01) ENTRIES IN '(&02)' STATEMENT TABLE

### Meaning

Output of a sort test run for systems engineers.
(&00): prefix
(&01): number of generated or modified entries
(&02): name of the statement table.
Message weight: 1.

## SRT1129

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1129 (&00) WARNING: ILLEGAL MESSAGE PRIORITY IN 'OPTION' STATEMENT. DEFAULT VALUE IS USED

### Meaning

A message priority value > 3 and <> 7 was specified for the MSG operand
of the OPTION statement.
(&00): prefix.
Message weight: 3.

## SRT1130

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1130 (&00) PLEASE ENTER SORT STATEMENTS

### Meaning

The sort/merge routine which was called up in interactive mode
requests the input of the statements.
(&00): prefix.
Message weight: 3.

## SRT1131

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1131 (&00) *** INPUT ERROR: LENGTH OF STATEMENT > 256 BYTES ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1132

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1132 (&00) *** STATEMENT READ ERROR X'(&01)' IN '(&02)' MACRO. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): error code
(&02): macro RDATA or RDSTMT/TRSTMT/CORSTMT.
Message weight: 3.

### Response

Check the macro error code and react accordingly.
Repeat the sort/merge run.

## SRT1133

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1133 (&00) WARNING: '(&01)' IN MERGE MEANINGLESS WITHOUT '(&02)' OPERAND

### Meaning

A CHECKPOINT or CKPT operand without the RECORDS-PER-CYCLE or
CYCLE operand in the MERGE-RECORDS or MERGE statement is not able to
set a checkpoint in a merge run.
Setting a checkpoint by means of the /SEND-MSG command is also
possible without specifying a CHECKPOINT or CKPT operand.
(&00): prefix
(&01): CHECKPOINT or CKPT operand
(&02): RECORDS-PER-CYCLE or CYCLE operand.
Message weight: 3.

## SRT1134

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1134 (&00) *** USER EXIT '(&01)' IN '(&02)' STATEMENT MISSING. RUN IS ABORTED ***

### Meaning

In the ASSIGN-EXITS, MODS statement or in the statement table, the
associated entry for user routine (&01) is missing for one of the sort
field formats PHYSICAL-TRANSLATE or TB, VIRTUAL-TRANSLATE or TR,
EXTERNAL-COMPARE or E.
(&00): prefix
(&01): user exit PHYSICAL-TRANSLATE or ETB,
VIRTUAL-TRANSLATE or ETR,
EXTERNAL-COMPARE or EXT/EXA.
(&02): statement ASSIGN-EXITS or MODS.
Message weight: 3.

### Response

Enter the missing user exit (&01) and repeat the run.

## SRT1135

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1135 (&00) *** USER EXITS 'E21, E23, EXT' NOT PERMITTED IN 31-BIT ADDRESS MODE. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Either use E15, E35, EXA user exits or work in 24-bit address mode.
Repeat the sort/merge run.

## SRT1136

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1136 (&00) *** USER EXIT '(&01)' WITH EXLST PARMOD=24 NOT SUPPORTED IN 31-BIT ADDRESS MODE. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): user exit EXLST-FOR-INPUT or E18, EXLST-FOR-OUTPUT or E39.
Message weight: 3.

### Response

Use EXLST PARMOD=31 or 24-bit address mode.
Repeat the sort/merge run.

## SRT1137

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1137 (&00) *** USER EXIT '(&01)' WITH EXLST >= BS2000 V9 NOT SUPPORTED WITH BS2000 < V9. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): user exit EXLST-FOR-INPUT or E18, EXLST-FOR-OUTPUT or E39.
Message weight: 3.

### Response

Use EXLST < BS2000 V9. Repeat the sort/merge run.

## SRT1138

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1138 (&00) *** 31-BIT ADDRESS MODE REQUIRES 'MODE' SPECIFICATION FOR USER EXIT '(&01)' ((&02)). RUN IS ABORTED ***

### Meaning

A mode specification must be made for user exit (&01) with name (&02) when
working in 31-bit address mode.
(&00): prefix
(&01): name of the user exit
(&02): name of the user exit routine.
Message weight: 3.

### Response

Make a mode specification for the user exit and repeat the sort/merge run.

## SRT1139

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1139 (&00) *** REFERENCE TO FCB NOT PERMITTED IN 31-BIT ADDRESS MODE. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Work without references to the FCB or use 24-bit address mode.
Repeat the sort/merge run.

## SRT1140

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1140 (&00) INVALID '(&01)' VALUE IN FIELD ENTRY (&02) OF '(&03)' STATEMENT

### Meaning

(&00): prefix
(&01): invalid value
(&02): number of the invalid field entry
(&03): SUM-RECORDS or SUM statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1141

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1141 (&00) MORE THAN (&02) ENTRIES IN '(&01)' STATEMENT

### Meaning

(&00): prefix
(&01): name of the invalid statement
(&02): Maximum number of field entries.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1142

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1142 (&00) INVALID '(&01)' VALUE IN FIELD ENTRY (&02) OF '(&03)' STATEMENT

### Meaning

(&00): prefix
(&01): designation of the invalid value
(&02): number of the invalid field entry
(&03): SELECT-INPUT-RECORDS or INCLUDE/OMIT statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1143

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1143 (&00) ILLEGAL FORMAT COMBINATION IN FIELD ENTRY (&01) OF '(&02)' STATEMENT

### Meaning

(&00): prefix
(&01): number of the errored field entry
(&02): SELECT-INPUT-RECORDS or INCLUDE/OMIT statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1144

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1144 (&00) INVALID '(&01)' VALUE IN '(&02)' STATEMENT

### Meaning

(&00): prefix
(&01): name of the invalid value
(&02): name of the statement or statement table.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1145

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1145 (&00) *** POSIX FILE NAMES TOO LONG ***

### Meaning

The sum of the name lengths of all POSIX input files exceeds the given
maximum.
(&00): prefix.
Message weight: 3.

### Response

process a lower number of files or shorten file names by omitting the
actual directory.
- Interactive mode: reenter corrected statement.
- Procedures, batch processing or level1: correct erroneous statement and
repeat the sort/merge run.

## SRT1146

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1146 (&00) *** POSIX FILES AND BS2000 FILES CANNOT BE USED AS INPUT FILES SIMULTANEOUSLY ***

### Meaning

In a SORT run either only POSIX files or only BS2000 files may be
used as input.
(&00): prefix.
Message weight: 3.

### Response

Use only one type of input files.
- Interactive mode: reenter corrected statement.
- Procedures, batch processing or level1: correct erroneous statement and
repeat the sort/merge run.

## SRT1147

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1147 (&00) TWO-DIGIT-YEAR ONLY ALLOWED FOR FORMAT ZONED-DECIMAL OR PACKED-DECIMAL

### Meaning

TWO-DIGIT-YEAR must only be specified for the formats ZONED-DECIMAL
or PACKED-DECIMAL.
(&00): prefix.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1148

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1148 (&00) TWO-DIGIT-YEAR AND SORTING FIELD LENGTH NOT EQUAL 2 OR 4

### Meaning

TWO-DIGIT-YEAR only allows a sorting field length of
2 (PACKED-DECIMAL or ZONED-DECIMAL) or 4 (PACKED-DECIMAL).
(&00): prefix.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1149

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1149 (&00) STATEMENTS WITH ISO-CCSN '(&01)' NOT SUPPORTED

### Meaning

Statements with an ISO-CCSN are not supported.
(&00): prefix.
(&01): statement CCSN.
Message weight: 3.

### Response

Correct the statement CCSN and repeat the run.

## SRT1150

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1150 (&00) STATEMENTS WITH UNICODE-CCSN '(&01)' NOT SUPPORTED

### Meaning

Statements with an Unicode-CCSN are not supported.
(&00): prefix.
(&01): statement CCSN.
Message weight: 3.

### Response

Correct the statement CCSN and repeat the run.

## SRT1151

Destination: USER-TASK Routing code: Weight:

Warranty : NO

SRT1151 (&00) Operand '(&01)' invalid: Error '(&02)'

### Meaning

The operand (&01) is invalid. Error cause is indicated by (&02):
(&02): 1. numeric value contains alphabetic character
2. numeric value is greater than maximum allowed.
(&00): Prefix.

### Response

Correct operand value according to specification and input the
statement again.

## SRT1155

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1155 (&00) FIELD ENTRIES IN '(&01)' STATEMENT MISSING

### Meaning

(&00): prefix
(&02): name of the statement or statement table.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1156

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1156 (&00) MORE THAN 99 FILES IN '(&01)' STATEMENT

### Meaning

(&00): prefix
(&02): name of the statement or statement table.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1157

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1157 (&00) INVALID '(&01)' VALUE IN FIELD ENTRY (&02) OF '(&03)' STATEMENT

### Meaning

(&00): prefix
(&01): invalid value
(&02): number of the field entry
(&03): SORT-RECORDS/MERGE-RECORDS or SORT/MERGE statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1158

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1158 (&00) REMAINDER FIELD NOT PERMITTED IN FIELD ENTRY (&01)

### Meaning

No remainder fields are permitted in the case of full record sorting
and merging.
(&00): prefix
(&01): number of the entry.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1159

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1159 (&00) WARNING: '(&01)' VALUE > '(&02)' VALUE IN '(&03)' STATEMENT

### Meaning

The entries in statement (&03) are illogical, since the set of records to
be sorted in one cycle is greater than the total set of records.
If the ESTIMATED-RECORDS or SIZE value is correct, cycle sorting is
suppressed although its execution was requested (RECORDS-PER-CYCLE or
CYCLE operand).
Processing continues.
(&00): prefix
(&01): RECORDS-PER-CYCLE or CYCLE operand
(&02): ESTIMATED-RECORDS or SIZE operand
(&03): SORT-RECORDS or SORT or
MERGE-RECORDS or MERGE statement.
Message weight: 1.

### Response

Check the values of the RECORDS-PER-CYCLE or CYCLE and ESTIMATED-RECORDS
or SIZE operands of the SORT-RECORDS / SORT or MERGE-RECORDS / MERGE
statement.

## SRT1161

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1161 (&00) WARNING: SPECIFIED SKIP1, SKIP2 OR BIAS VALUE IGNORED IN MERGE RUN

### Meaning

The SKIP1, SKIP2 or BIAS operand was specified in a merge run, but was
simply ignored as it is not required.
(&00): prefix.
Message weight: 2.

## SRT1162

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1162 (&00) WARNING: '(&01)' VALUE IGNORED IN REMAINDER FIELD OF SORT FIELD ENTRY (&02)

### Meaning

(&00): prefix
(&01): invalid value
(&02): number of the field entry.
Message weight: 2.

## SRT1163

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1163 (&00) WARNING: '(&01)' VALUE IGNORED IN FIELD ENTRY (&02) WHEN 'FORMAT=(&03)'

### Meaning

(&00): prefix
(&01): invalid value
(&02): number of the invalid field entry
(&03): format BINARY or BI.
Message weight: 2.

## SRT1166

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1166 (&00) WARNING: LENGTH(&01) > LENGTH(&02) IN '(&03)' STATEMENT

### Meaning

The illogical length entry is ignored (LENGTH4 and/or LENGTH5) and
processing continues.
(&00): prefix
(&01),(&02): record length values
LENGTH2 = maximum internal record length
LENGTH4 = minimum internal record length
LENGTH5 = average internal record length
(&03): SET-RECORD-ATTRIBUTES or RECORD statement.
Message weight: 3.

### Response

Check the record length values in the SET-RECORD-ATTRIBUTES or
RECORD statement.

## SRT1167

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1167 (&00) WARNING: <LENGTH4> AND <LENGTH5> OF 'RECORD' STATEMENT IGNORED WITH 'TYPE=F'

### Meaning

The length specifications <length4> and <length5> will be ignored when
sorting fixed-length records.
(&00): prefix.
Message weight: 0.

## SRT1168

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1168 (&00) INVALID USER EXIT NAME IN 'MODS' STATEMENT

### Meaning

(&00): prefix.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1169

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1169 (&00) ACTION FOR USER EXIT '(&01)' IN 'MODS' STATEMENT INVALID OR DUPLICATED

### Meaning

(&00): prefix
(&01): name of the user exit.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1170

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1170 (&00) USER EXIT '(&01)' USED MORE THAN ONCE IN 'MODS' STATEMENT

### Meaning

(&00): prefix
(&01): name of the user exit.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1 and 2: correct the statement and
repeat the sort/merge run.

## SRT1171

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1171 (&00) *** '(&01)' STATEMENT MISSING. RUN IS ABORTED ***

### Meaning

Neither the statement (&01) nor the corresponding statement table was
specified for the sort/merge run. Or the statement/statement table was
not complete.
(&00): prefix
(&01): missing statement: SORT-RECORDS or SORT,
MERGE-RECORDS or MERGE,
MODIFY-CODE or NEWCOL,
END.
Message weight: 3.

### Response

Enter the missing (&01) statement or specify the missing statement
table or complete it. Repeat the sort/merge run.

## SRT1172

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1172 (&00) *** '(&01)=YES' IN '(&02)' STATEMENT AND SORT OR SUM FIELDS NOT IN FIRST 4092 BYTES. RUN IS ABORTED ***

### Meaning

The operand KEEP-EQUAL-SEQUENCES=YES or EQUALS=YES was specified and some
sort fields or sum fields are located outside the first 4092 bytes.
(&00): prefix
(&01): KEEP-EQUAL-SEQUENCES or EQUALS operand
(&02): SORT-RECORDS or SORT statement.
Message weight: 3.

### Response

Check the field entries in the SORT-RECORDS or SORT, SUM-RECORDS or SUM
statements. Repeat the sort/merge run with corrected statements
or statement tables.

## SRT1173

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1173 (&00) WARNING: '(&01)=YES' IN '(&02)' STATEMENT IS IGNORED IN COMBINATION WITH SUM FIELDS

### Meaning

The operand KEEP-EQUAL-SEQUENCES=YES or EQUAL=YES in the SORT-RECORDS
or SORT statement will be ignored, because a SUM-RECORDS or SUM
statement has been specified.
(&00): prefix
(&01): KEEP-EQUAL-SEQUENCES or EQUALS operand
(&02): SORT-RECORDS or SORT statement.
Message weight: 2.

### Response

Do not specify KEEP-EQUAL-SEQUENCES or EQUALS when totalling records.

## SRT1174

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1174 (&00) WARNING: MATCH CONSTANT IN FIELD ENTRY (&01) OF '(&02)' STATEMENT SHORTENED TO LENGTH OF CORRESPONDING FIELD

### Meaning

The match constant is truncated
- left-justified in the case of formats BINARY/BI and CHARACTER/CH
- right-justified in the case of formats FIXED-POINT/FI,
PACKED-DECIMAL/PD and ZONED-DECIMAL/ZD.
(&00): prefix
(&01): number of the field entry
(&02): SELECT-INPUT-RECORDS or INCLUDE/OMIT statement.
Message weight: 2.

## SRT1178

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1178 (&00) *** SUM FIELD (&01) NOT AT BEGINNING OF FIELD (&02) IN '(&03)' STATEMENT. RUN IS ABORTED ***

### Meaning

A sum field with an extension does not start at the first byte
of a remainder or constant field. The run is aborted.
(&00): prefix
(&01): number of the sum field entry
(&02): number of the sort field entry
(&03): SORT-RECORDS or SORT statement.
Message weight: 3.

### Response

Check and correct the field specifications in the SUM-RECORDS, SUM
statement or statement table and in the SORT-RECORDS, SORT
statement or statement table. Repeat the sort run.

## SRT1179

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1179 (&00) WARNING: MASK FIELD OVERLAP IN SORT FIELD (&01) (REMAINDER FIELD) AND SUM FIELD (&02). MASK IN REMAINDER FIELD IGNORED

### Meaning

The sort/merge routine has detected an overlap between a remainder
field with a mask and a sum field with a mask.
The mask in the remainder field will be ignored. The sort run continues.
(&00): prefix
(&01): number of the remainder field with a mask
(&02): number of the sum field with a mask.
Message weight: 2.

## SRT1180

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1180 (&00) *** FIELD OVERLAPPING OF SUM FIELDS (&01) AND (&02). RUN IS ABORTED ***

### Meaning

Sum fields must not overlap with other sum fields or with sort fields.
(&00): prefix
(&01),(&02): numbers of the sum fields which overlap.
Message weight: 3.

### Response

Check and correct the field specifications in the SUM-RECORDS or SUM
statement or in the statement table. Repeat the run.

## SRT1181

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1181 (&00) *** ILLEGAL FIELD OVERLAPPING OF SUM FIELD (&01) AND SORT FIELD (&02). RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): number of the sum field
(&02): number of the sort field.
Message weight: 3.

### Response

Check and correct the field specifications in the SUM-RECORDS or SUM
and SORT-RECORDS or SORT statements or statement table.
Repeat the run.

## SRT1182

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1182 (&00) *** ILLEGAL FIELD OVERLAPPING OF SORT FIELDS (&01) AND (&02). RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01),(&02): numbers of the sort fields which overlap.
Message weight: 3.

### Response

Check and correct the specifications for the overlapping sort fields
in the SORT-RECORDS, SORT, MERGE-RECORDS or MERGE statement, or
statement table. Repeat the run.

## SRT1183

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1183 (&00) WARNING: FIELD OVERLAP IN SORT FIELDS (&01) AND (&02). UNDEFINED RESULTS POSSIBLE

### Meaning

The run continues.
(&00): prefix
(&01),(&02): numbers of the sort fields which overlap.
Message weight: 1.

## SRT1184

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1184 (&00) 'ED MASKS' ONLY PERMITTED WITH FORMATS '(&01)'

### Meaning

A mask was specified for a field which has neither the format
BINARY/BI nor FIXED-POINT/FI nor PACKED-DECIMAL/PD nor ZONED-DEZIMAL/ZD.
(&00): prefix
(&01): formats BINARY,FIXED-POINT, PACKED-DECIMAL, ZONED-DECIMAL or
BI, FI, PD, ZD.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1185

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1185 (&00) *** 'ED MASKS' ONLY PERMITTED WITH SELECT SORT. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Repeat the sort run as a record selection sort.

## SRT1186

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1186 (&00) WARNING: FOR PRINTING SORT WILL ONLY CONSIDER THE 4 LEAST SIGNIFICANT BYTES OF FIELD ENTRY (&01)

### Meaning

In the BI or FI formats, only one word (4 bytes) can be cosidered for
print editing. In the case of longer fields, only the rightmost 4 bytes
are used.
(&00): prefix
(&01): number of the field entry.
Message weight: 2.

## SRT1187

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1187 (&00) NUMBER OF OPENING PARENTHESES IN '(&01)' STATEMENT NOT EQUAL TO NUMBER OF CLOSING PARENTHESES

### Meaning

A more precise description of the error is given by the following
messages SRT1101 and SRT1102.
(&00): prefix
(&01): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1188

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1188 (&00) INVALID 'ED MASK' IN FIELD ENTRY (&01) OF '(&02)' STATEMENT

### Meaning

The ED MASK in field entry (&01) of statement (&02) is missing or longer
than 254 characters.
(&00): prefix
(&01): number of the field entry which contains the invalid mask
(&02): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the statement and
repeat the sort/merge run.

## SRT1189

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1189 (&00) WARNING: '(&01)' VALUE IGNORED IN MASK FIELD OF SORT FIELD ENTRY (&02)

### Meaning

An editing mask was specified for sort field (&02). The EL operand value
for this sort field is therefore ignored.
The run continues.
(&00): prefix
(&01): invalid value
(&02): number of the field entry.
Message weight: 2.

## SRT1190

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1190 (&00) WARNING: '(&01)' STATEMENT IGNORED

### Meaning

The MODIFY-CODE or NEWCOL statement will be ignored since none of the
sort fields has the MODIFY-CODE or NC format.
The run continues.
(&00): prefix
(&01): MODIFY-CODE or NEWCOL statement.
Message weight: 1.

## SRT1191

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1191 (&00) WARNING: USER EXIT '(&01)' IN '(&02)' STATEMENT IGNORED

### Meaning

The user exit (&01) will be ignored because no format
PHYSICAL-TRANSLATE/TB, VIRTUAL-TRANSLATE/TR or no sort sequence
EXTERNAL-COMPARE/E has been specified in a sort field. The run continues.
(&00): prefix
(&01): user exits PHYSICAL-TRANSLATE or ETB,
VIRTUAL-TRANSLATE or ETR,
EXTERNAL-COMPARE or EXT/EXA
(&02): ASSIGN-EXITS or MODS statement.
Message weight: 1.

## SRT1192

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1192 (&00) WARNING: SYMBOLIC NAME '(&01)' IN '(&02)' STATEMENT SHORTENED TO LENGTH 20

### Meaning

The symbolic name contains more than 20 characters and is truncated
on the right. The sort/merge run continues by reading in
the next statement.
(&00): prefix
(&01): symbolic name
(&02): name of the invalid statement.
Message weight: 3.

### Response

Use symbolic names with a maximum length of 20 characters.

## SRT1193

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1193 (&00) SYMBOLIC NAME '(&01)' OF '(&02)' STATEMENT NOT DEFINED

### Meaning

The symbolic name (&01) has to be specified by the ADD-SYMBOLIC-NAMES
statement in accordance with its subsequent function in the (&02)
statement
as a field, constant or print mask before it can be used in the
(&02) statement.
(&00): prefix
(&01): symbolic name
(&02): name of the invalid statement.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1:
Specify the symbolic name via the ADD-SYMBOLIC-NAME statement and
reenter the (&02) statement.

## SRT1194

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1194 (&00) SYMBOLIC NAME '(&01)' USED MORE THAN ONCE IN 'ADD-SYMBOLIC-NAMES' STATEMENT

### Meaning

No symbolic name may be used more than once in the ADD-SYMBOLIC-NAMES
statement.
(&00): prefix
(&01): symbolic name.
Message weight: 3.

### Response

- Interactive mode: reenter the ADD-SYMBOLIC-NAMES statement with
different symbolic names.
- Procedures, batch processing or level 1: enter different symbolic names
in the ADD-SYMBOLIC-NAMES statement and repeat the sort/merge run.

## SRT1195

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1195 (&00) *** USER EXITS 'INPUT, OUTPUT, EXTERNAL-COMPARE' WITH 'PARAMETER-MODE=24' NOT PERMITTED IN 31-BIT ADDRESS MODE. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Either specify PARAMETER-MODE=ANY or use 24-bit address mode.

## SRT1196

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1196 (&00) WARNING: STATEMENT FILES IGNORED BECAUSE 'ASSIGN-FILES' STATEMENT READ FROM STATEMENT FILE

### Meaning

A statement file must not contain an ASSIGN-FILES statement with the
specification of statement files.
The run continues.
(&00): prefix.
Message weight: 3.

## SRT1197

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1197 (&00) *** ERROR WHEN ASSIGNING SYSDTA TO FILE '(&01)'. RUN IS ABORTED ***

### Meaning

An error occurred when assigning SYSDTA to a statement file or to SYSCMD.
(&00): prefix
(&01): name of the statement file or SYSCMD.
Message weight: 3.

### Response

Check whether the statement file exists and if it is a SAM or ISAM
file with variable record length.

## SRT1198

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1198 (&00) PLEASE CORRECT STATEMENT

### Meaning

The last statement to be entered contained semantic errors, which are
explained by previous messages.
(&00): prefix.
Message weight: 3.

### Response

Correct the invalid operands.

## SRT1199

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1199 (&00) 'FIELDS=COMPLETE-RECORD' IN THE 'SORT-RECORDS' STATEMENT ONLY PERMITTED FOR RECORD SORT

### Meaning

(&00): prefix.
Message weight: 3.

### Response

- Interactive mode: reenter the corrected statement.
- Procedures, batch processing or level 1: correct the invalid statement
and repeat the sort/merge run.

## SRT1201

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1201 (&00) *** SORTIN AND SORTIN01 NOT PERMITTED SIMULTANEOUSLY. RUN IS ABORTED ***

### Meaning

The simultaneous use of file link names SORTIN and SORTIN01 is not
permitted during the assignment of input files.
(&00): prefix.
Message weight: 3.

### Response

Check the file link names and repeat the run after making the
appropriate corrections.

## SRT1202

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1202 (&00) *** CHECK '(&01)' RELATION: CALCULATED NUMBER OF SCRATCH FILES > 99. RUN IS ABORTED ***

### Meaning

The specifications in the ESTIMATED-RECORDS or SIZE and
RECORDS-PER-CYCLE or CYCLE operands have led the sort/merge routine to
calculate more than 99 scratch files.
(&00): prefix
(&01): ESTIMATED-RECORDS/RECORDS-PER-CYCLE or SIZE/CYCLE.
Message weight: 3.

### Response

Check the specifications for the ESTIMATED-RECORDS or SIZE and
RECORDS-PER-CYCLE or CYCLE operands and also the sort strategy. Repeat
the run.

## SRT1203

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1203 (&00) *** LEVEL2 SUPPORT WITH INCOMPLETE FCB REFERENCE TABLE. RUN IS ABORTED ***

### Meaning

During transfer of the control information on level 2, SORT has detected
that the FCB reference table is incomplete.
(&00): prefix.
Message weight: 3.

### Response

Complete the FCB reference table and repeat the run.

## SRT1204

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1204 (&00) *** SORTWK AND SORTWK1 NOT PERMITTED SIMULTANEOUSLY. RUN IS ABORTED ***

### Meaning

The file link names SORTWK and SORTWK1 must not be used simultaneously
during the assignment of work files. The run is aborted.
(&00): prefix.
Message weight: 3.

### Response

Check the file link names and repeat the run after making the
appropriate corrections.

## SRT1205

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1205 (&00) *** INPUT MISSING: NEITHER INPUT FILE NOR USER EXIT '(&01)' DEFINED. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): user exit INPUT or E15/E21.
Message weight: 3.

### Response

Assign the input file or define input via user exit INPUT or E15/E21.
Then repeat the run.

## SRT1206

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1206 (&00) *** OUTPUT MISSING: NEITHER OUTPUT FILE NOR USER EXIT '(&01)' DEFINED. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): name of user exit OUTPUT or E35/E23.
Message weight: 3.

### Response

Assign the output file or define output via user exit OUTPUT or E35/E23.
Then repeat the run.

## SRT1207

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1207 (&00) WARNING: NUMBER OF MERGE INPUT FILES NOT EQUAL TO 'FILES' OPERAND IN 'MERGE' STATEMENT

### Meaning

The run continues.
(&00): prefix.
Message weight: 3.

### Response

Check and correct link names MERGExx and the FILES operand in the MERGE
statement.
Repeat the run with corrected values.

## SRT1208

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1208 (&00) *** OUTPUT FILE WITH FIXED RECORD FORMAT: BLOCK SIZE TOO SMALL FOR RECORD SIZE. RUN IS ABORTED ***

### Meaning

The block size of the output file is smaller than the output record length
or, in the case of ISAM files, smaller than the output record length + 4.
(&00): prefix.
Message weight: 3.

### Response

Check and correct the output file block size and output record size.
Repeat the run with corrected values.

## SRT1209

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1209 (&00) *** ILLEGAL MERGE APPLICATION. RUN IS ABORTED ***

### Meaning

The following merge applications are not permitted:
- changing the record type in a merge run
- extending the sum fields in a merge run
- sort access method in a merge run.
(&00): prefix.
Message weight: 3.

### Response

Either modify the operands for the merge run or use a sort run instead.

## SRT1211

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1211 (&00) *** RECORD LENGTH IN '(&01)' STATEMENT > MAX. RECORD LENGTH (32759 BYTE). RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): SET-RECORD-ATTRIBUTES or RECORD statement.
Message weight: 3.

### Response

Check and correct the length specifications in the SET-RECORD-ATTRIBUTES
or RECORD statement. Repeat the run with corrected values.

## SRT1212

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1212 (&00) *** INPUT FILES WITH ACCESS METHOD 'BTAM' NOT PERMITTED FOR TAG SORTING. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check and correct the access method of the input files and the
SORT-RECORDS or SORT statement.

## SRT1213

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1213 (&00) *** TAG SORTING IS NOT POSSIBLE FOR INPUT FILES ON TAPE OR IN POSIX. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Assign the disk file and check and correct the SORT-RECORDS or
SORT statement. Repeat the run.

## SRT1214

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1214 (&00) *** MULTIFILE SORT/MERGE: INPUT RECORD FORMATS NOT IDENTICAL. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check that the input file record formats are identical and repeat the run
with corrected values.

## SRT1215

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1215 (&00) *** INPUT FILES WITH DIFFERENT RECORD LENGTHS NOT PERMITTED FOR FIXED RECORD FORMAT. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check and correct the record lengths of the input files. Repeat the run
with corrected values.

## SRT1216

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1216 (&00) *** TAG SORTING: ACCESS METHODS OF INPUT FILES NOT IDENTICAL. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the input files and repeat the run with corrected values.

## SRT1218

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1218 (&00) *** MULTIFILE SORT/MERGE: INPUT FILE NOT PERMITTED AS OUTPUT FILE. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the file assignments and, if necessary, repeat the run with
corrected values.

## SRT1219

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1219 (&00) WARNING: SORTIN EQUAL TO SORTOUT WITHOUT 'INOUT=YES' IN 'OPTION' STATEMENT

### Meaning

For security reasons the input file should not be used as an output file
without confirmation from the user (INOUT=YES in the OPTION statement).
The run continues.
(&00): prefix.
Message weight: 2.

### Response

Check the file assignments and repeat the run after specifying operand
INOUT=YES in the OPTION statement.

## SRT1220

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1220 (&00) *** TAG SORTING: SORTIN MUST NOT BE EQUAL TO SORTOUT. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the file assignments and repeat the run with corrected
specifications.

## SRT1221

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1221 (&00) WARNING: SORTIN AND SORTOUT NOT EQUAL, BUT 'INOUT=YES' IN 'OPTION' STATEMENT

### Meaning

INOUT=YES will be ignored. The run continues.
(&00): prefix.
Message weight: 0.

### Response

Check the file assignments.

## SRT1222

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1222 (&00) WARNING: RECORD SIZE OF INPUT FILE NOT EQUAL TO <LENGTH1>. <LENGTH1> WILL BE IGNORED

### Meaning

The record length defined for the input file does not agree with the
input record length <length1> defined in the SET-RECORD-ATTRIBUTES
or RECORD statement.
The run continues.
(&00): prefix.
Message weight: 3.

### Response

Check the file attributes of the input file and the
specifications in the SET-RECORD-ATTRIBUTES or RECORD statement.

## SRT1223

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1223 (&00) *** '(&01)' STATEMENT INVALID: RECORD LENGTH MISSING. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): SET-RECORD-ATTRIBUTES or RECORD statement.
Message weight: 3.

### Response

Specify the length in the SET-RECORD-ATTRIBUTES or RECORD statement and
repeat the run.

## SRT1224

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1224 (&00) *** FIELDS OUTSIDE OF RECORD. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the field specifications in the statements and repeat the run with
corrected values.

## SRT1225

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1225 (&00) *** RECORD SIZE OF OUTPUT FILE NOT EQUAL TO <LENGTH3>. RUN IS ABORTED ***

### Meaning

The record length defined for the output file does not agree with the
output record length <length3> defined in the SET-RECORD-ATTRIBUTES
or RECORD statement or calculated by SORT.
(&00): prefix.
Message weight: 3.

### Response

Check the file attributes of the output file and the specifications in the
SET-RECORD-ATTRIBUTES or RECORD statement and repeat the run with
corrected values.

## SRT1226

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1226 (&00) *** MERGE RUN: CHANGING RECORD FORMAT FROM 'FIXED' TO 'VARIABLE' NOT PERMITTED. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the record formats of the input/output files and of the
SET-RECORD-ATTRIBUTES or RECORD statement and repeat the run
with corrected values.

## SRT1227

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1227 (&00) WARNING: REQUEST FOR CHANGE OF RECORD LENGTH IGNORED. FALSIFICATIONS POSSIBLE

### Meaning

The request for a change of record length (because of the length entries
in the SET-RECORD-ATTRIBUTES or RECORD statement) will be ignored.
The run continues.
(&00): prefix.
Message weight: 3.

### Response

Check whether the result was falsified by an incorrect record length
specification.

## SRT1228

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1228 (&00) WARNING: CHANGE OF RECORD LENGTH OR FORMAT IN USER EXIT '(&01)' EXPECTED. FALSIFICATIONS POSSIBLE

### Meaning

If records with invalid lengths are passed to SORT, unpredictable
results are possible. The run continues.
(&00): prefix
(&01): user exit INPUT or E15/E21, or OUTPUT or E35/E23.
Message weight: 0.

### Response

Check whether the result was falsified by an incorrect record length
specification.

## SRT1229

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1229 (&00) WARNING: RECORD FORMAT OF INPUT FILE NOT EQUAL TO RECORD FORMAT SPECIFIED IN '(&01)' STATEMENT

### Meaning

The record format of the input file does not agree with the record format
specified in the INPUT or TYPE operand of the SET-RECORD-ATTRIBUTES or
RECORD statement. The record format specified in the statement will be
ignored.
(&00): prefix
(&01): SET-RECORDS-ATTRIBUTES or RECORD statement.
Message weight: 3.

## SRT1230

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1230 (&00) WARNING: TAG SORTING WITH MULTIPLE INPUT FILES: NO FILE INDICATOR IN ADDRESS FIELD

### Meaning

The run continues.
(&00): prefix.
Message weight: 2.

### Response

Ensure that the record contains a file indicator.

## SRT1231

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1231 (&00) *** RECORD LENGTH FIELD NOT ELIMINATED IF OUTPUT RECORD FORMAT IS VARIABLE. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Correct the SORT-RECORDS or SORT statement and repeat the run.

## SRT1232

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1232 (&00) *** WITH '(&01)=YES' RECORD LENGTH FIELD MUST NOT BE USED AS SORT FIELD. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): KEEP-EQUAL-SEQUENCES or EQUALS operand.
Message weight: 3.

### Response

Correct the SORT-RECORDS or SORT statement and repeat the run.

## SRT1233

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1233 (&00) *** WHEN CHANGING RECORD FORMAT FROM 'VARIABLE' TO 'FIXED' RECORD LENGTH FIELD MUST NOT BE USED AS SORT FIELD. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Correct the SORT-RECORDS or SORT statement and repeat the run.

## SRT1234

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1234 (&00) *** INVALID RECORD FORMAT FOR OUTPUT FILE. RUN IS ABORTED ***

### Meaning

The attributes of the output file do not match the attributes
of the input file or the attributes of output or input files
are not valid or incomplete.
(&00): prefix.
Message weight: 3.

### Response

Check the attributes of the output/input file and of the statements.
Repeat the run with corrected values.

## SRT1235

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1235 (&00) *** RECORD LENGTH FIELD MUST NOT BE USED AS SUM FIELD. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Correct the SUM-RECORDS or SUM statement and repeat the run.

## SRT1236

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1236 (&00) *** RECORD LENGTH FIELD MUST NOT BE USED AS SORT FIELD WITH SORT FIELD FORMAT '(&01)' ***

### Meaning

(&00): prefix.
(&01): format of the sort field.
Message weight: 3.

### Response

Use only format
- CH / CHARACTER
- BI / BINARY
- FI / FIXED-POINT
for record length field. Repeat the run.

## SRT1237

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1237 (&00) *** ISAM OUTPUT FILE: LENGTH OF ISAM KEY > 255 BYTES. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the file attributes of the output file and repeat the run with
corrected values.

## SRT1238

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1238 (&00) *** ISAM OUTPUT FILE: KEY POSITION NOT EQUAL TO START OF HIGHEST SORT FIELD. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the file attributes of the output file and the specification
in the SORT-RECORDS/SORT or MERGE-RECORDS/MERGE statement.
Repeat the run with corrected values.

## SRT1239

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1239 (&00) *** ISAM OUTPUT FILE: KEY OUTSIDE OF RECORD. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the file attributes of the output file and the specifications
in the SORT-RECORDS/SORT or MERGE-RECORDS/MERGE statement.
Repeat the run with corrected values.

## SRT1240

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1240 (&00) *** ISAM OUTPUT FILE: INVALID ISAM KEY. RUN IS ABORTED ***

### Meaning

The ISAM key for the output file and the associated sort fields defined in
the SORT-RECORDS or SORT statement do not satisfy the conditions laid down
by DMS (e.g. descending sorting order).
(&00): prefix.
Message weight: 3.

### Response

Check the file attributes and the specifications in the SORT-RECORDS/SORT
or MERGE-RECORDS/MERGE statement.
Repeat the run with corrected values.

## SRT1244

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1244 (&00) *** AVAILABLE WORK AREA TOO SMALL FOR FCB GENERATION. RUN IS ABORTED ***

### Meaning

The memory space available for the complex SORT application is too small
to accommodate the management of the FCB's (file control blocks).
(&00): prefix.
Message weight: 7.

### Response

Split up the application over several sort runs.

## SRT1250

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1250 (&00) *** SORT/MERGE APPLICATION TOO COMPLEX ((&01) ROUTINE > 4096 BYTES). RUN IS ABORTED ***

### Meaning

The (&01) routine exceeds the size of a CORE page (4096 byte) and thus
also
the effective range of the used base register.
(&00): prefix
(&01): name of the SORT routine.
Message weight: 3.

### Response

Simplify the sort/merge application and repeat the run.

## SRT1251

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1251 (&00) *** ENTRY FOR FILE '(&01)' IN FCB REFERENCE TABLE REFERS TO 31-BIT FCB. RUN IS ABORTED ***

### Meaning

If an FCB reference table is used (FCB = File Control Block), you are not
allowed to use a 31-bit FCB.
(&00): prefix
(&01): name of the file with the 31-bit FCB
OUT for an output file
IN,IN01...IN99 for an input file
WK,WK1...WK9 for a work file
WK01...WK99 for a scratch file
CKPT for a checkpoint file.
Message weight: 3.

### Response

Either use 24-bit FCB or work without an FCB reference table.
Correct the program and repeat the sort/merge run.

## SRT1252

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1252 (&00) *** FOR OUTPUT FILE BLOCK SIZE NOT POSSIBLE ON A 4K FORMATTED PVS. RUN IS ABORTED ***

### Meaning

Files on a 4K formatted PVS can only be created with a block size
of (STD,2) or a multiple of (STD,2).
(&00): prefix.
Message weight: 3.

### Response

Change the block size of the output file. Repeat the run.

## SRT1253

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1253 (&00) *** BLKCTRL VALUE '(&01)' NOT POSSIBLE FOR OUTPUT FILE. RUN IS ABORTED ***

### Meaning

The following BLKCTRL values are not permitted:
- BLKCTRL=PAMKEY on a NONKEY-PVS.
- BLKCTRL=DATA2K on a 4k formatted PVS.
- BLKCTRL=DATA4K, if the block size is not even-numbered.
(&00): prefix
(&01): BLKCTRL value.
Message weight: 3.

### Response

Modify the specified BLKCTRL value and repeat the run.

## SRT1254

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1254 (&00) *** MULTIFILE SORT/MERGE: DIFFERENT CODED-CHARACTER-SET-NAMES NOT ALLOWED. RUN IS ABORTED ***

### Meaning

If there are several input files, all of them must have the same
coded character set name.
(&00): prefix.
Message weight: 3.

### Response

Change the coded character set name with the /MODIFY-FILE-ATTRIBUTES
or /CATALOG command or convert the file into the corresponding
coded character set with the utility routine PERCON.
Repeat the run.

## SRT1255

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1255 (&00) *** INVALID SORT TABLE FOR CODED CHARACTER SET NAME '(&01)'. RUN IS ABORTED ***

### Meaning

The SORT table requested by XHCS-SYS is ambiguous. Several characters
are converted. It is not possible to create a table to reconvert the
codes.
(&00): prefix
(&01): coded character set name.
Message weight: 3.

### Response

Inform the system administrator and correct the SORT table.
Repeat the run.

## SRT1256

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1256 (&00) WARNING: CODED CHARACTER SET NAME IN 'SET-RECORD-ATTRIBUTES' STATEMENT IS IGNORED

### Meaning

The coded character set name may only be defined with the
SET-RECORD-ATTRIBUTES statement if there is no input file available.
The run continues.
(&00): prefix.
Message weight: 2.

## SRT1257

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1257 (&00) *** SUBSYSTEM 'XHCS-SYS' NOT AVAILABLE IN SYSTEM. RUN IS ABORTED ***

### Meaning

SORT requires tables for the following functions. These are provided by
XHCS-SYS:
- SORT requires a SORT table for the EXTENDED-CHARACTER and
TRANSLATE-CHARACTER SORT field formats.
- If the coded character set of the statements does not match the data,
SORT requires a conversion table.
These functions may not be used if the subsystem XHCS-SYS is not
available.
If a statement file has a CCSN other than EDF03IRV, XHCS-SYS also must be
available in the system.
(&00): prefix.
Message weight: 3.

### Response

Implement XHCS-SYS in order to be able to use the functions described.
Repeat the run.

## SRT1258

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1258 (&00) *** UNKNOWN CODED CHARACTER SET NAME '(&01)'. RUN IS ABORTED ***

### Meaning

The coded character set name (&01) is unknown to XHCS-SYS. This means
that a SORT table cannot be requested from SORT or the statement file
cannot be used.
(&00): prefix
(&01): coded character set name.
Message weight: 3.

### Response

Correct the coded-character-set-name of the input or statement file
with the /MODIFY-FILE-ATTRIBUTES or /CATALOG command, or define it
with the SET-RECORD-ATTRIBUTES statement if the input file is missing.
Repeat the run.

## SRT1259

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1259 (&00) *** ERROR X'(&01)' IN MACRO '(&02)'. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): macro error code
(&02): name of the macro.
Message weight: 3.

### Response

Check macro error code and react accordingly.
Repeat the run.

## SRT1260

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1260 (&00) *** CONSTANT IN '(&01)' STATEMENT CANNOT BE CONVERTED TO CODED CHARACTER SET OF DATA. RUN IS ABORTED ***

### Meaning

Possible reasons:
- Coded character set name of the statement is unknown or not compatible
with the coded character set of the data.
- Constant characters do not exist in the coded character set
of the data.
(&00): prefix
(&01): name of the statement
Message weight: 3.

### Response

Check the coded character set name of the statement and data.
Convert the statement to the coded character set used by the data
or only use characters in the constants that are defined in the
coded character set used by the data.
Repeat the run.

## SRT1261

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1261 (&00) *** SORT FIELD FORMAT '(&01)' ILLEGAL FOR ISAM KEY. RUN IS ABORTED ***

### Meaning

SORT fields which form the ISAM key must not be defined with the
EXTENDED-CHARACTER or TRANSLATE-CHARACTER format.
(&00): prefix
(&01): SORT field format.
Message weight: 3.

### Response

Use the CHARACTER format or a SAM output file.
Repeat the run.

## SRT1262

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1262 (&00) *** ERROR X'(&01)' DURING DYNAMIC LOADING OF MODULE '(&02)' FROM LIBRARY '(&03)'. RUN IS ABORTED ***

### Meaning

Possible reasons:
- The library is not available.
- There is no module in the library with the name (&02).
(&00): prefix
(&01): error code
(&02): name of the module
(&03): name of the library.
Message weight: 3.

### Response

Create module for the coded character set (&02) or do not use
TRANSLATE-CHARACTER format.
Repeat run.

## SRT1263

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1263 (&00) *** ERRORS IN '(&01)' TABLES OF THE '(&02)' LIBRARY. RUN IS ABORTED ***

### Meaning

If the TRANSLATE-CHARACTER format is used, SORT needs two tables which
are reloaded from the library (&02).
The following restrictions apply to the tables in this library:
- If X'00' is found in the first table, it must also be found in the
second table.
- In the code area of a character used as replacement character
X'00' must be found in the second table.
The run is aborted.
(&00): prefix
(&01): coded character set name
(&02): name of the library.
Message weight: 3.

### Response

Correct invalid tables in the library.
Repeat the run.

## SRT1264

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1264 (&00) *** TAG SORTING NOT POSSIBLE OWING TO SIZE OF INPUT FILE '(&01)'. RUN is ABORTED ***

### Meaning

If the file size is 32 GB or more, over 3 bytes are required for the
block address. However, only 3 bytes are available in the retrieval
address.
(&00): prefix.
(&01): name of input file.
Message weight: 3.

### Response

PAM input file: Select sort type selection sort or full sort
SAM input file: Select sort type tag sort with extended address
(*TAG-COMPOUND) or selection sort or full sort.

## SRT1265

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1265 (&00) *** ERRORS IN '(&01)' TABLES OF USER EXIT 'TRANSLATE-CHARACTER'. RUN IS ABORTED ***

### Meaning

If the TRANSLATE-CHARACTER format is used, SORT needs two tables which
are reloaded by user exit 'TRANSLATE-CHARACTER'.
The following restrictions apply to the tables:
- If X'00' is found in the first table, it must also be found in the
second table.
- In the code area of a character used as replacement character
X'00' must be found in the second table.
The run is aborted.
(&00): prefix
(&01): coded character set name
Message weight: 3.

### Response

Correct invalid tables.
Repeat the run.

## SRT1301

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1301 (&00) *** INPUT RECORD LENGTH > MAX. RECORD LENGTH. RUN IS ABORTED ***

### Meaning

During dynamic checking of the variable record length in the course of
processing, an input record has been found which is longer than the
specified maximum length.
(&00): prefix.
Message weight: 3.

### Response

Check the record lengths of the input records and correct the
specifications in the SET-RECORD-ATTRIBUTES or RECORD statement.
Repeat the run.

## SRT1302

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1302 (&00) *** CONTROL FIELD EXCEEDS RECORD END. RUN IS ABORTED ***

### Meaning

During dynamic checking of the variable record length in the
course of processing, a record has been found with control fields
which do not lie within the record.
(&00): prefix.
Message weight: 3.

### Response

Correct the specifications in the SORT-RECORDS/SORT or
MERGE-RECORDS/MERGE statement and repeat the sort/merge run.

## SRT1303

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1303 (&00) *** ATTRIBUTES OF INPUT FILE '(&01)' INCORRECT. RUN IS ABORTED ***

### Meaning

(&00): prefix
(&01): file link name of the SORT input file.
Message weight: 3.

### Response

Check the file attributes and repeat the run with corrected values.

## SRT1304

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1304 (&00) *** INVALID RETURN CODE X'(&01)' FROM USER EXIT '(&02)'. RUN IS ABORTED ***

### Meaning

User exit (&02) has produced return code X'(&01)', which is not
permitted for this call.
(&00): prefix
(&01): return code
(&02): name of the user exit.
Message weight: 3.

### Response

Check the user routine and repeat the run with corrected values.

## SRT1305

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1305 (&00) *** ATTRIBUTES OF OUTPUT FILE INCORRECT. RUN IS ABORTED ***

### Meaning

(&00): prefix.
Message weight: 3.

### Response

Check the file attributes and repeat the run with corrected values.

## SRT1306

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1306 (&00) *** FILE '(&01)': RECORD LENGTH > MAXIMUM RECORD LENGTH PERMITTED. RUN IS ABORTED ***

### Meaning

This message refers to the output file or a scratch file.
- Output file: the variable length of an output record is greater than the
maximum output record length or the specified block size is not large
enough to accommodate the whole record in the output block.
- Scratch files with BLKCTRL=DATA on disks: the length of the sort records
is limited to 32752 bytes.
(&00): prefix
(&01): link name of the file concerned.
Message weight: 3.

### Response

- Output file: increase the maximum output record length or block size or
leave the computation of the block size to the sort/merge routine.
- Scratch file: use scratch files on tapes, create scratch files on disk
with BLKCTRL=PAMKEY or ask the system administrator to set the
class 2 option BLKCTRL to PAMKEY.

## SRT1307

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1307 (&00) *** ERROR DURING TAG SORTING: NO MORE THAN 255 RECORDS IN INPUT BLOCK POSSIBLE. RUN IS ABORTED ***

### Meaning

The tag address generated by SORT for a record contains only one byte
for the record number in the block.
(&00): prefix.
Message weight: 3.

### Response

Check whether reducing the input block size makes the tag sort possible.
Once the input block size has been corrected, repeat the run.

## SRT1308

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1308 (&00) *** ILLEGAL ORDER: MISPLACED SORT ACCESS METHOD MACRO 'SRT(&01)'. RUN IS ABORTED ***

### Meaning

The sort/merge program discovered the access method macro SRT(&01)
in an unexpected place. The sequence of the macros
(SRTOPEN > SRTPUT > SRTGET > SRTCLSE) was not observed.
Possible causes of error:
- Duplicated SRTOPEN
- SRTPUT, SRTGET or SRTCLSE without SRTOPEN
- SRTPUT after SRTGET.
(&00): prefix
(&01): name of the incorrectly positioned macros (OPEN, PUT, GET, CLSE).
Message weight: 3.

### Response

Check the user program and correct errors.
Repeat the run.

## SRT1309

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1309 (&00) *** LEADING DIGITS <> 0 TRUNCATED DURING MASK PROCESSING. RUN IS ABORTED ***

### Meaning

When shortening the edit field to the appropriate mask length,
significant leading digits were truncated.
The run is aborted.
(&00): prefix.
Message weight: 3.

### Response

Extend the mask length and repeat the sort run with corrected values.

## SRT1310

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1310 (&00) *** WARNING : MACRO CATAL FOR SORTOUT NOT SUCCESSFUL. RC = (&01) ***

### Meaning

The attemp to store a CCSN for the SORTOUT data set by CATAL
was not successful.
For error reason see return code.
(&00): prefix.
(&01): CATAL return code.
For more detailed information about the error code enter
/HELP-MSG DMS(&01). Most frequently cases are:
0599 : CCSN operand not supported.
05CB : CATAL for strange user id
06C8 : CATAL for data set generation group
Message weight: 3.

### Response

Store CCSN later or ignore it.

## SRT1311

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1311 (&00) *** SYNTACTICAL ERROR IN SORT VERSION '(&01)'. RUN IS ABORTED ***

### Meaning

The syntax of the version given as parameter of a SORT subprogram call
is incorrect.
Following syntax of version is allowed:
n.n / n.na / n.nann
nn.n / nn.na / nn.nann
(n: decimal character / a: alphabetic character)
(&00): prefix
(&01): wrong version
Message weight: 3.

### Response

Check the version and repeat the run after correcting the version.

## SRT1312

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1312 (&00) *** SORT VERSION '(&01)' NOT AVAILABLE IN SYSTEM. RUN IS ABORTED ***

### Meaning

A SORT version required by a program call is not installed.
The run is aborted.
(&00): prefix
(&01): SORT version required
Message weight: 3.

### Response

Choose another version or have the required version installed in system.

## SRT1314

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1314 (&00) *** SUBSYSTEM '(&01)' NOT AVAILABLE IN SYSTEM. RUN IS ABORTED ***

### Meaning

(&00): prefix.
(&01): name of subsystem.
Message weight: 3.

### Response

Repeat the SORT run when subsystem will be available.

## SRT1315

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1315 (&00) *** ERROR CODE '(&01)' IN MACRO 'GETINSV'. RUN IS ABORTED ***

### Meaning

(&00): prefix.
(&01): macro error code
Message weight: 3.

### Response

Check macro error code and react accordingly. Repeat the run.

## SRT1316

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1316 (&00) *** ERROR CODE '(&01)' IN MACRO 'GETINSP' FOR LOGID '(&02)'. RUN IS ABORTED ***

### Meaning

(&00): prefix.
(&01): macro error code.
(&02): logical identifier of data set requested.
Message weight: 3.

### Response

Check macro error code and react acordingly.
Repeat the run .

## SRT1317

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

SRT1317 (&00) *** BS2000 VERSION < '(&01)'. RUN IS ABORTED ***

### Meaning

(&00): prefix .
(&01): BS2000 version needed.
Message weight: 3.

### Response

SORT needs at least the BS2000 version (&01).

©2023 Fujitsu Technology Solutions GmbH | BS2000 System Messages