00

0000

Completed normally.
Function completed normally.

00

0001

Completed as negotiated.

Function completed as negotiated.

00

0003

Data available. Returned by test conversation if data has arrived on the posted conversation.

00

0004

Control information available.

Returned by test conversation if control information has arrived on the posted conversation.

00

0086

Logic error.

01

0001

Program not attached.

The transaction issued another verb before issuing an attach verb. The program must attach efore calling other verbs.

01

0002

Duplicate attach attempted.

After a previous attach verb and before a detach verb, the transaction program attempted to reissue the attach verb.

01

0003

Invalid conversation ID (rsrc unknown).

The conversation specified in the cnvid parameter is not a valid conversation.

01

0004

Context not set.

01

0009

Null structure pointer parameter passed.

A verb was called with a null structure pointer as a parameter.

01

0010

Attach: path is a required parameter.

The configuration file path is required for attach and rattach.

01

0011

Attach: LU name is a required parameter.

The LU name is required for attach type AT_LU(0).

01

0012

Attach: Invalid attach type parameter.

Valid attach types for a transaction program are AT_LU(0) AT_NODE(1).

01

0013

Attach: LU unknown.

The specified LU is not configured.

01

0014

Attach: LU not available, limits reached.

The LU specified in the attach is not activated, or has already reached the configured limit of attached transaction programs.

01

0015

Attached: TP name is not configured.

The transaction program name specified in the request is not configured.

01

0016

Attach, rattach: Configuration file not authorized or invalid.

Cannot authorize attach.

The attach failed because the transaction program process does not have access permission to the node, the node is not active, or the attach verb configuration file parameter was incorrect.

01

0017

Rattach: Conversation ID required.

Conversation ID required for remote attach.

01

0018

Rattach: Invalid conversation ID for rattach.

The conversation specified in the remote attach is invalid or cannot be remotely attached.

01

0019

Attach, rattach: Invalid wait-time parameter.

Invalid wait-time. Valid wait parameters are 0, 1, 2, ..., or -1 to specify no maximum wait time.

01

0020

Attach: Not enough space. Attach rejected.

Not enough space to support the transaction program.

01

0021

Attach: SNA Scheduler TP limit reached. Attach rejected.

The SNA Scheduler process limit has been reached.

01

0022

Attach: Not enough space in TP.

01

0023

Attach: Pathname is too long.

01

0030

Alcnv: Partner (rlu) is a required parameter.

Remote LU name is required.

01

0031

Alcnv: Mode name is a required parameter.

Mode name is required.

01

0032

Alcnv: Program name (tpn) is a required parameter.

Remote transaction program name is required.

01

0033

Alcnv: Partner LU (rlu) not found. Remote LU unknown.

The specified remote LU is not configured for the attached LU.

01

0034

Alcnv: Mode not found. Mode unknown.

The specified mode is not configured between the remote LU and the attached LU.

01

0035

Alcnv: Invalid parameter (type).

Invalid alcnv type. Valid conversation types for alcnv are 0 for basic conversation and 1 for mapped conversation.

01

0036

Alcnv: Mapped verb interface not allowed.

Mapped conversations not available. Either the attached LU or the remote LU is not configured to support mapped conversations, or the transaction program name specified in the previous attach is not configured to support mapped conversations.

01

0037

Alcnv: Basic verb interface not allowed. Basic conversations not available.

The transaction program name specified in the previous attach is not configured to support basic conversations.

01

0038

Alcnv: Invalid parameter (when).

Invalid session allocation parameter. Valid session allocation parameters for alcnv are AC_WHEN(0), AC_DELAY(1), and AC_IMMED(2).

01

0039

Alcnv: Delayed allocation not allowed. No delayed session allocation.

The attached LU is not configured to support delayed session allocation.

01

0040

Alcnv: Immediate allocation not allowed. No immediate session allocation.

The attached LU is not configured to support delayed session allocation.

01

0041

Alcnv: Invalid parameter (sync).

Invalid sync-level parameter. Valid sync level parameters for alcnv are 0 for NONE and 1 for CONFIRM processing.

01

0042

Alcnv: Requested sync level not allowed. Requested sync level not available.

The requested sync-level support must be configured for the requested mode and for the transaction program name specified in the previous attach request.

01

0043

Alcnv: PIP not allowed. No PIP data.

PIP data-support must be configured for the transaction program name specified in the previous attach request.

01

0044

Alcnv: Invalid PIP length. PIP data too large.

Too many PIP parameters were passed in the PIP data, or the PIP data exceeds the maximum length.

01

0045

Alcnv: Invalid parameter (sec).

Invalid security-level parameter. Valid security-level parameters are SEC_NONE(0), SEC_SAME(1), and SEC_PGM(2).

01

0046

Alcnv: Requested security not allowed. Requested security level not available.

The requested security-level support is not configured. SEC_SAME(1) must be configured for the attached LU and the remote LU. SEC_PGM(2) must be configured for the attached LU, the remote LU, and for the transaction program name specified in the previous attach request.

01

0047

Alcnv: Invalid format for user parameter.

01

0048

Alcnv: Invalid format for password parameter.

01

0049

Invalid mode name. Mode name SNASVCMG cannot be specified when using a mapped conversation.

01

0060

Cnfrm, cnfrmed: Conflict with conversation sync level.

Sync level conflict. A cnfrm or cnfrmed verb was attempted on a conversation that was allocated sync level NONE.

01

0070

Dalcnv: Invalid parameter (type).

Invalid dalcnv type. Valid dalcnv types are:

DC_SYNC(1)

DC_FLUSH(2)

DC_AB_PGM(3)

DC_AB_SVC(4)

DC_AB_TMR(5)

DC_LOCAL(6)

DC_CNFRM(7)

Invalid mdalcnv types are:

DC_AB_PGM(3)

DC_AB_SVC(4)

DC_AB_TMR(5)

Valid mdalcnv types are:

DC_SYNC(1)

DC_FLUSH(2)

DC_LOCAL(6)

DC_CNFRM(7)

DC_ABEND(8)

01

0080

Prprcv: Invalid parameter (type).

Invalid prprcv type. Valid prprcv types are 0 for FLUSH and 1 for SYNC.

01

0081

Prprcv: Invalid parameter (lock).

Invalid prprcv lock parameter. Valid prprcv lock parameters are 0 for Short lock, and 1 for Long lock. This parameter is significant for prprcv type SYNC.

01

0090

Rcvwt, pstrct: Invalid parameter (fill).

Invalid fill parameters for rcvwt and pstrct are RW_BUFF(0) and RW_LL(1).

01

0091

Invalid parameter (length) cannot be negative.

Negative length is invalid. The length parameter is negative.

01

0100

Snddta: Invalid LL.

Invalid LL field. The data passed to snddta contains an invalid LL field of 0x0000, 0x8000, or 0x8001.

01

0101

Snddta: Invalid LL within the data stream. PS headers not supported.

The data passed to snddta contains an LL field of 0x0001, which indicates a PS header. This is not supported.

01

0102

Mapping Error: Map name not found.

01

0103

Mapping Error: Map execution failure.

01

0104

Mapping Error: Duplicate map name.

01

0110

Snderr: Invalid parameter (type).

Invalid snderr type. Valid snderr types for transaction programs are SE_PGM(1) and SE_SVC(0).

01

0111

Snderr: SE_ALC(2) is reserved.

01

0120

Waitcv: Negative count value is invalid.

Negative waitcv count is invalid.

01

0121

Waitcv: Invalid conversation ID on list. Invalid conversation for waitcv.

The list parameter passed to waitcv contained an invalid conversation ID.

01

0122

Waitcv: Listed conversation ID does not have posting active.

01

0123

Waitcv: No conversation with posting is active.

If a list of conversations was passed to waitcv, none of the conversations had posting active. If no list was passed, then no conversations for the TP had posting active.

01

0124

Waitcv: List size (count) must be positive. Waitcv requires list when non-zero count specified.

When the waitcv request specifies one or more conversations in the count parameter, those conversations must be passed in the list parameter. No list parameter was passed.

01

0125

Waitcv: List size (count) too large. Waitcv list too large.

The number of conversations specified in the waitcv request exceeds the ability of the verb interface layer to process the request.

01

0130

Testcv: Invalid parameter (type).

01

0131

Testcv: Posting not active for conversation.

01

0140

Setctx: Path required if tcbid is supplied.

01

0141

Setctx: Requested context not found.

01

0300

Not authorized to CO verbs. TP not authorized to the type of Control Operator verb issued.

01

0301

Requested limits are invalid.

Limits requested in CNOS verb are invalid.

01

0302

Service Manager Mode not initialized.

CNOS verb issued before service manager mode is initialized.

01

0310

Session limit of 0 is invalid.

Session limit must be greater than 0.

01

0311

Responsible value invalid.

Invalid responsible parameter.

01

0312

C_maxs must be greater than c_minf + c_minb.

Sum of the minimum first-speaker sessions and the minimum bidder sessions cannot exceed session limit.

01

0313

Dctses: Invalid parameter (immediate).

01

0314

Rstsl: Invalid parameter (dtrg).

01

0315

Rstsl: Invalid parameter (dsrc).

01

0316

Rstsl: Invalid parameter (force).

01

0320

Next session identifier not found.

01

0321

Invalid session identifier.

01

0400

Name must be less than 20 characters. Node Operator: String parameter too long.

Maximum name length is 20 characters.

01

0401

Line is a required parameter. Node Operator: Line name is required.

01

0402

LU is a required parameter. Node Operator: LU name is required.

01

0403

PU is a required parameter. Node Operator: PU name is required.

01

0404

Actsta: Invalid parameter (dial). Node Operator: Invalid dial parameter.

Valid dial parameters are 0, 1, 2.

01

0410

Rspque must be NULL. Node Operator: Response queue name unsupported this release.

01

0411

Chgmsgq: Severity must be between 0 and 99.

01

0501

Invalid local LU.

The fully qualified LU name of the local LU specified on the dfnllu is invalid.

01

0502

Invalid remote LU.

The value specified in the local LU session-limit parameter of the dfnllu verb is less than the sum of the currently defined LU mode session limits.

01

0503

Invalid mode.

01

0504

Invalid ALS.

01

0505

Invalid Send Pacing Window.

01

0506

Invalid Receive Pacing Window.

01

0507

Invalid Max RU Upper Bound.

01

0508

Invalid Max RU Lower Bound.

01

0509

Invalid Sync Level option.

01

0510

Invalid Single Session Reinitialization option.

01

0511

Invalid Cryptography option.

01

0512

Invalid Maximum Number Sessions.

Parallel-session support (YES) is specified on the dfnrlu verb but the local LU session limit is 1.

01

0513

Invalid Minimum Number First Speaker.

Parallel-session support (YES) and CNOS support (NO) are specified on the dfnrlu verb.

01

0514

Invalid Minimum Number First Prebound.

CNOS support (YES) and parallel-session support (NO) is not specified on the dfnrlu verb.

01

0516

Invalid Blank Mode option.

01

0517

Invalid Network Name operator.

01

0518

Invalid Network Qualifier operator.

01

0519

Invalid Network Name.

01

0520

Invalid Network Qualifier.

01

0521

Invalid Init Type.

01

0522

Invalid Parallel Session option.

The fully qualified LU name of the remote LU specified on the dfnmode verb is not currently defined for the local LU.

01

0523

Invalid CNOS ALS.

01

0524

Invalid LU Password.

01

0525

Invalid Security Acceptance option.

01

0526

Invalid Password operation.

01

0527

Invalid LU Session Limits.

01

0528

Invalid Conversation Security.

01

0529

Invalid Security operation.

01

0530

Invalid User ID.

01

0531

Invalid Password.

01

0532

Invalid Profile.

01

0533

Invalid Wait.

01

0534

Invalid Max Number of TPs.

01

0535

Invalid LU ID Number.

01

0536

Invalid TP Name.

01

0537

Invalid Status.

01

0538

Invalid Conversation Type.

01

0539

Invalid Security Required.

01

0540

Invalid PIP option.

01

0541

Invalid PIP Number.

01

0542

Invalid PIP check.

01

0543

Invalid Data Mapping.

01

0544

Invalid FMH.

01

0545

Invalid Privilege.

01

0546

Invalid LUW Indicator.

01

0550

Invalid LU.

01

0551

Invalid Partner.

01

0552

Invalid ALS.

01

0553

Not enough space to complete operation.

01

0554

Invalid Remote PU.

01

0555

Invalid Line.

01

0556

Logic error: LSCB not found.

01

0557

Dfnsta: Associated Line not inactive.

01

0558

Logic error: ALCB not found.

01

0560

Dfnmode: Invalid Parameter.

01

0561

Dfnmode: Lower Bound exceeds Upper Bound.

01

0562

Dfnmode: Single Session Reinit not compatible with Partner.

01

0564

Defend: Minf cannot be greater than maxs.

01

0565

Dfnmode: Minpf cannot be greater than minf.

01

0566

Dfnmode: Maxs not compatible with partner.

01

0567

Dfnmode: Blank mode already exists.

01

0570

Dfnrlu: Cnosals and parallel session support not compatible.

01

0571

Dfnrlu: Parallel session support not compatible with maxs.

01

0574

Dfnrlu: Invalid reinit option for parallel-session support.

01

0575

Dfnrlu: CNOS also unknown.

01

0576

Dfnrlu: Null net name already exists.

01

0577

Dfnrlu: Parallel support not compatible with PU type.

01

0580

Logic error: drcb for local PU does not exist.

01

0581

Dfnllu: Session limits exceed LU session limits specified.

01

0582

Dfnllu: Network name specified after initsl.

01

0583

Dfnllu: Security parameters to be deleted not found.

01

0584

Dfnllu: LU ID already specified.

01

0585

Dfnllu: LU ID must be specified when lucb is initialized.

01

0586

Dfnllu: LU ID cannot be updated when session limit initialized.

01

0590

Dfnllu: Security access parameters conflict with security required.

01

0591

Dfnllu: Security parameters to be deleted not found.

01

0600

Too many resources defined—no internal address available.

01

0601

Invalid Exchange ID.

01

0602

Invalid Master Device.

01

0603

Invalid Monitor Timer.

01

0604

Invalid NOOP Messages.

01

0605

Invalid LOG Messages.

01

0606

Invalid Debug Messages.

01

0607

Invalid PU Name.

01

0608

Invalid CPU ID.

01

0609

Invalid Line Name.

01

0610

Invalid Line Type.

01

0611

Invalid Device Name.

01

0612

Invalid SDLC Role.

01

0613

Invalid Connection Type.

01

0614

Invalid NRZI.

01

0615

Invalid Half-duplex.

01

0616

Invalid Max BTU.

01

0617

Invalid Max Retries.

01

0618

Invalid Idle.

01

0619

Invalid Nonprod Rcv Time.

01

0620

Invalid Max I-Frames.

01

0621

Invalid Rate.

01

0622

Invalid SDLC Address.

01

0623

Invalid Phone Name.

01

0624

Dfnsta: Exceeded maximum number of stations (8).

01

0626

Dfnline: Multidrop specified and role not primary.

01

0627

Dfnsta: One station already defined for leased line.

01

0628

Dfnline: Line already exists.

01

0630

Dfnsta: Line not specified.

01

0631

Dfnsta: PU not specified.

01

0632

Dfnsta: Station already exists.

01

0634

Dspline: Invalid line name.

01

0635

Dspline: End of line list.

01

0636

Dspline: No lines defined.

01

0637

Dspcp: Invalid control point name.

01

0638

Dspcp: End of PU list.

01

0639

Dspcp: No PUs defined.

01

0640

Dltcbl: Mode unknown.

01

0641

Dltcbl: TP Name unknown.

01

0642

Dltcbl: Object is in use.

01

0646

Dltcbl: Local LU name not specified.

01

0647

Dltcbl: Remote LU name not specified.

01

0648

Dltcbl: No parameters specified.

01

0650

Dfnrpu: Neither XID or CPID specified.

01

0651

Dfnrpu: Both XID and CPID specified.

01

0659

Control point is not a host.

01

0660

Dspllu: Userid invalid.

01

0661

Dspllu: End of security list.

01

0662

No userid found.

01

0663

Dspllu: Invalid profile.

01

0664

Dspllu: Invalid LU name.

01

0665

Dspllu: End of LU list.

01

0666

Dspllu: No LU defined.

01

0667

Dsprlu: Invalid Remote LU name.

01

0668

Dsprlu: No more Remote LUs.

01

0669

Dsprlu: No Remote LUs defined.

01

0670

Dspmode: Invalid mode name.

01

0671

Dspmode: End of mode list.

01

0672

Dspmode: No modes defined.

01

0673

Dsptp: Invalid TP name.

01

0674

Dsptp: End of TP list.

01

0675

Dsptp: No TP defined.

01

0676

Dsptp: No Network Name.

01

0677

Invalid NEXT parameter value.

01

0691

Control point name is required.

01

0692

No more remote LUs or secondary LUs.

01

0693

LU_ID value does not match any LU.

01

0830

User crash code not described.

01

0850

s2_schd is not active.

The SNA Scheduler is not active.

01

0860

s2_schd has terminated abnormally.

The SNA Scheduler is no longer active. The transaction program has been detached.

01

0870

Time out—request not recovered.

01

0880

Time out—request recovered.

01

0890

Time out—message queue full.

01

0900

Verb logic error.

An internal logic error occurred while processing the verb.

01

0901

Duplicate s2_tpi.

Duplicate TPI attach attempted.

01

1000

Invalid NAU name.

The NAU must be no greater than eight characters and all characters must be of symbol-string Type A.

01

1001

Invalid NAU type.

Valid values are P_PU and P_LU.

01

1002

Invalid when parameter.

Valid values for sndru are P_WHEN and P_NONE. Valid values for alnau are P_WHEN and P_IMMED.

01

1003

Invalid block parameter.

Valid values are P_BLOCK and P_NBLOCK.

01

1004

Invalid bind parameter.

Buffer length is greater than zero and no bind pointer supplied.

01

1005

Resources temporarily unavailable. Retry.

01

1006

Not enough TP space to allocate another NAU.

01

1008

Not enough resources.

An attempt was made to send an RU that exceeds the maximum send size when sndru is issued in non-blocking mode.

01

1009

Null structure pointer supplied to a PI verb.

01

1010

Invalid structure type supplied for initpi.

01

1011

NAU identifier invalid.

The NAU identifier supplied on the verb call is not the nauid of a currently allocated NAU.

01

1012

Specified NAU not allocated.

An attempt was made to use the nauid of an NAU that is pending allocation.

01

1013

Invalid svcid.

Service identifier is not one of the valid values or is inconsistent with the NAU type specified on the alnau verb.

01

1014

The pointer to the pru structure is NULL.

This is a required field.

01

1015

The RU command is zero.

01

1016

The pointer to the RU buffer is NULL.

In this verb call, the RU buffer is required.

01

1017

The pointer to the ufsm structure is NULL.

This is a required field for the gfsm verb.

01

1018

RU sense data is required.

Zero is an invalid value.

01

1019

The flow parameter of the ssync verb is invalid.

Valid values are P_SND, P_RCV, and P_FLOW.

01

1020

The wait parameter is invalid.

Valid values are P_WAIT, P_NOWAIT, or a positive numeric value representing the time, in seconds, that the verb should wait.

01

1021

The loc_pac parameter is invalid.

This is an optional field, but if specified, valid values are P_PACE and P_NPACE.

01

1022

Required UFSM pointer is NULL.

The pointer to the ufsm structure is NULL. This field is required on the rcvru verb and on the alnau verb issued with block = P_BLOCK.

01

1023

svcid inconsistent with NAU type.

The svcid parameter is compatible with the nau type of the specified NAU.

01

1024

The dfnslu verb was issued while LU 0-3 was not configured by

the configuration manager.

01

1025

LU not defined.

A secondary LU with the name specified in naunm is not currently defined.

01

1026

LU not available.

The LU specified on the alnau verb is already allocated.

01

1027

PU not defined.

A PU with the name specified in naunm is not currently defined.

01

1028

PU not available.

The PU specified on the alnau verb is already allocated.

01

1030

Attach type is not specified.

The Transaction Program that issued the verb did not attach with attach type AT_ANODE or AT_ALU.

01

1031

Send check.

The reply to the sndru verb received from the SNA Scheduler indicated a send check.

01

1032

Negative response.

The reply to the sndru verb received from the SNA Scheduler indicated a negative response.

01

1033

Receive check.

The reply to the sndru verb received from the SNA Scheduler indicated a receive check.

01

1034

Session lost.

02

0001

No information for conversation.

02

0002

Conversation not posted.

02

0003

Request-to-send not received.

03

0001

Conversation State error.

Request is illegal in the current conversation state.

03

0002

Logical Record State error.

Request is illegal because the current logical record has not been completed.

03

0003

Conv for waitcv not S2_RECV.

A conversation specified in the waitcv request is not in receive state.

05

0001

Remote TP not available—no retry.

The transaction program could not be started on the remote system because of a lack of resources, which is not temporary. Retry is not suggested.

05

0002

Remote TP not available—retry.

The transaction program could not be started on the remote system because of a temporary resource shortage. Retry is suggested.

05

0003

Remote LU does not support conversation type.

The remote LU does not support the requested conversation type.

05

0004

PIP data not supported by remote.

Program initialization data is not supported by the remote LU.

05

0005

PIP specification error.

Program initialization data was specified incorrectly.

05

0006

Invalid access security information.

Security information was not specified correctly.

05

0007

Remote program does not support requested sync level.

05

0008

Remote TP not recognized by remote LU.

The transaction program requested was not recognized at the remote LU.

05

0009

Allocation failure—no retry.

05

0010

Allocation failure—retry.

05

0011

First Speaker session not available.

The session is not immediately available.

05

0012

Local resource allocation failure.

05

0013

Cannot authorize security access.

05

0022

Allocation rejected by Resource Manager.

05

0099

Unknown sense code data received.

07

0001

Program Error: Current logical record not truncated.

Partner has reported a program error; the current logical record was not truncated.

07

0002

Program Error: Current logical record truncated.

Partner has reported a program error; current logical record was truncated.

07

0003

Program Error: Data may have been purged.

Partner has reported a program error; current logical record may have been purged.

07

0011

Service Error: Current logical record not truncated.

Service Transaction Program has reported an error; current logical record was not truncated.

07

0012

Service Error: Current logical record was truncated.

Service Transaction Program has reported an error; current logical record was truncated.

07

0013

Service Error: Data may have been purged.

Service transaction program has reported a program error; current logical record may have been purged.

07

0020

Mapping Error: FMH not supported.

07

0021

Mapping Error: Mapping not supported.

09

0000

Normal deallocation by partner.

Partner has deallocated the conversation.

09

0001

Abnormal deallocation by partner.

Partner has terminated the conversation abnormally.

09

0002

Abnormal deallocation by service program.

A service transaction program has terminated the conversation abnormally.

09

0003

Abnormal deallocation verb time-out.

Time-out has occurred.

09

0004

Abnormal deallocation, Session Failure.

The session has failed.

09

0005

Abnormal deallocation by partner.

10

0063

Limits not zero.

10

0064

Requested limits exceed configuration.

This error should be interpreted as ACTIVATION_FAILURE_RETRY

10

0065

Sum of minimums exceed maximum session.

The sum of the minimum first-speaker and bidder sessions exceeds the requested maximum.

10

0066

Invalid SNASVCMG limits.

SNASVCMG limits must be 2: 1 bidder and 1 first speaker.

10

0067

SNASVCMG mode not initialized.

10

0068

Mode limits are closed.

10

0069

Chgsl not valid for this mode.

10

0070

SNASVCMG mode not reset, other modes still not reset.

SNASVCMG mode cannot be reset because user modes are still open.

10

0071

CNOS race with remote—remote won.

10

0072

Partner does not recognize mode.

10

0073

CNOS is in process locally.

10

0074

CNOS allocation error.

10

0075

CNOS resource failure.

The SNASVCMG session with the partner LU either could not be started or failed.

10

0076

Insufficient space for a new session.

10

0077

Partner LU is not active.

10

0078

Modes incompatible: session not started.

11

0001

Node operator verb failure.

11

0002

Node operator verb not recognized.

11

0003

Attach of type AT_NODE.

Transaction Program must attach with type AT_NODE to use node operator verbs.

11

0010

Link name not recognized.

11

0011

Adjacent link station not recognized.

11

0012

Physical unit not recognized.

11

0013

Earlier request still active.

11

0014

Dial in or dial out required.

11

0015

Logical unit name not recognized.

11

0016

Message queue name not recognized.

11

0017

Message queue not enabled.

11

0018

No message in message queue.

11

0100

Actpu failure.

11

0110

Actlu failure.

11

0120

Dctpu failure.

11

0130

Dctlu failure.

11

0140

Chgmsgq failure.

11

0150

Dspmsgq failure.

11

0190

Rtvnmsg failure.