Skip to content

SER8000 - 8850

SER8000 SEROSTRM

SerNet output streamer Transforms and transmits Mdus to clients

SER8000E {userid} SEROSTRM {tca_address} invoked with nothing to send

Explanation: Internal error.

Solution: Try to determine what userid was doing at the time the error message was produced. If userid sseems to be doing something reasonable and the message still occurs contact Micro Focus Customer Care.

SER8001W {userid} SEROSTRM {tca_address} ignored a response Mdu due to an earlier error

Explanation: Warning.

SER8002E {userid} SEROSTRM {tca_address} XML generator initialization failed with rc={return code}, rsn={reason code}

Explanation: Internal error.

Solution: If the error is repeatable, Try using the NETWORK trace, to see what the XML looks like (F SRNETSTC,NT,ON,USER=USERID,SIZE=1024). See the ChangeMan ZMF Installation guide, Appendix B Modify Commands. Record return code and reason code, contact Micro Focus Customer Care.

SER8003E {userid} SEROSTRM {tca_address} CCSID {ccsidfrom} to {ccsidto} conversion failed with rc={return code}, rsn={reason code}

Explanation: Internal error.

Solution: This may be a Unicode configuration issue. See the discussion for message SER2500 earlier in this chapter. Look up the return code and reason code in z/OS Unicode Services User’s Guide and Reference - SA38-0680-xx and proceed accordingly.

SER8004E {userid} SEROSTRM {tca_address} CCSID conversion initialization failed with rc={return code}, rsn={reason code}

Explanation: Internal error.

Solution: This may be a Unicode configuration issue. See the discussion for message SER2500 earlier in this chapter. Look up the return code and reason code in z/OS Unicode Services User’s Guide and Reference - SA38-0680-xx and proceed accordingly.

SER8005E {userid} SEROSTRM {tca_address} change direction failed with receiverc={return code}

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8006E {userid} SEROSTRM {tca_address} change direction failed with check rc={return code}

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8007E {userid} SEROSTRM {tca_address} send failed with rc={return code}

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8008E {userid} SEROSTRM {tca_address} invalid record length prefix.

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8100

SER8101E Rejectedsssssss1 mmmmmmm1 ooooooo1 with sssssss2 mmmmmmm2 ooooooo2

Explanation: An invalid sequence of requests was detected. The previous service/ message/scope is not the same as the incoming service/message/scope.

Solution: Report this error to Micro Focus Customer Care.

SER8102E Received invalid compressed data, rc=xxxx

Explanation: An attempt at expanding the incoming, compressed request data failed with the detailed return code.

Solution: Report this error to Micro Focus Customer Care.

SER8104E uuuuuuuu portname Unidentifiable message received, header is11111111 22222222 IP=ip-addr:port

Explanation: Warning. Either an invalid length or an invalid sequence indicator was detected. The 8 bytes of the request header are printed in hex as 11111111 22222222. The ip-addr:port shows the IP address and port that the invalid request is originating from.

SER8105E uuuuuuuu SerIstrmttttttttcould not determine which ECB was posted

Explanation: A logic error occurred in the wait processing of request management.

Solution: Report this error to Micro Focus Customer Care.

SER8106E uuuuuuuu SerIstrmttttttttreceived a nnnn byte message but conversation state VCASTATE ss is now invalid, VCAWHATR=rr

Explanation: A logic error occurred in conversation management.

Solution: Report this error to Micro Focus Customer Care.

SER8114E A short message arrived from some non Sernet client and is rejected.

Explanation: A request was received that was of a length less than the expected minimum.

Solution: If this error persists report it to Micro Focus Customer Care.

SER8115E uuuuuuuu Unexpected request received rrrrrrrr

Explanation: An unrecognized request was received from the Sernet main task.

Solution: If this error persists report it to Micro Focus Customer Care.

SER8200 SERUSER

SerNet User Subtask in the server. Process conversations. receive request message data units (Mdus), handle connections, and route Mdus to their applications according to the given product, object, and message.

SER8200E {product} {object} {message} request rejected, logon is required

Explanation: User must be logged on.

SER8201E SERUSER {tca_address} denied access by user {userid} because maximum users are logged on

Explanation: Maximum users reached.

Solution: Try again later.

SER8202E {userid} SERUSER {tca_address} rejected a downlevel client, client vrm={VRM}

Explanation: Client code is older than server code.

Solution: Upgrade the Client code.

SER8203E User {real-userid} is not authorized to impersonate user {userid}

Explanation: Probably a security definition issue.

Solution: Contact your security administrator.

SER8204I Password permanently changed on your security system

Explanation: Information.

SER8205E Invalid user ID specified

Explanation: Error.

Solution: Correct the userid.

SER8206E Password expired - you must specify a new password

Explanation: Information.

Solution: Specify a new password.

SER8207E Invalid password specified

Explanation: This is dependent on your installation, for example, maybe you tried a password which has recently been used. Your installation may have rules preventing this.

Solution: Contact your security administrator.

SER8208E Logon authorization failed - RC={return code} Reason={reason code}

Explanation: SERLCSEC has issued return code and reason code.

Solution: Examine SERLCSEC, determine if the exit is working properly.

SER8209I Logon accepted for user {userid}; Local CCSID={coded character set identifier}

Explanation: This message is displayed when a TSO user successfully connects to the SERNET started task.

Solution: No action required.

SER8210E Session rejected because no initial logon

SER8211E Unsupported request {object} {message} rejected

Explanation: Internal error, valid OBJECT/MESSAGE combinations are CONNECT LOGON, CONNECT PASSWORD, CONNECT LOGOFF, and CONNECT START.

Solution: Contact Micro Focus Customer Care.

SER8212W Logoff unsuccessful because user is not logged on

Explanation: Warning.

SER8213I User {userid} logged off

Explanation: Information.

SER8214I {message-number} {message}

Explanation: SAF message, for example ICH408I USER(USER252 ) GROUP(USER).

SER8215W User {userid} disconnected

Explanation: Warning.

SER8216E User {userid} no XCH security environment created

Explanation: A RACF VERIFY call was issued to SERLCSEC which failed to cause an ACEE to be created. The lack of an ACEE is a security problem so the connect request is blocked.

Solution: Check SERLCSEC and, if in doubt, contact Micro Focus Customer Care.

SER8218EuuuuuuuuError in SIOCTTLSCTL request, Rc=xxxxErrNo=yyyy

Explanation: The TLS certificate provided in the logon request failed verification with the TCP/IP return code xxxx and Errno yyyy.

Solution: Correct the TLS certificate and retry the logon request.

SER8219EuuuuuuuuNo user associated with the TLS client certificate

Explanation: The TLS certificate provided in the logon request was not associated with a particular userid.

Solution: Correct the TLS certificate and retry the logon request.

SER8220EuuuuuuuuWrong user associated with the TLS client certificate –cccccccc`

Explanation: The userid associated with the TLS certificate provided was different from the one specified in the logon request.

Solution: Correct the TLS certificate or logon userid and retry the logon request.

SER8221E Rejected {tca-address} {initial-product} {initial object} {initial-message} with {this-product} {this-object} {this-message}

Explanation: Transmission error.

Solution: Contact Micro Focus Customer Care.

SER8222E Received invalid compressed data, rc={CODE}

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8223I {userid} Mail command: {command}

Explanation: Information.

SER8224E New request rejected while responding to {object} {message} request

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8225E {userid} SERUSER {tca-address} received a request message with invalid lrecl {lrecl} (VmruLRLn)

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8226E {userid} SERUSER {tca-address} could not determine which ECB was posted

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8227E The server is terminating, request rejected

Explanation: Information.

SER8228E Data chunking request rejected, chunking is not allowed

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8230E {userid} SERUSER {tca-address} received a {integer} byte message but conversation state VCASTATE {conversation-state} is now invalid, VCAWHATR={what-received}

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8231E {userid} SERUSER {tca-address} rejected a connection request with multiple message blocks

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8232I userid Login credentials found

Explanation: A connection request was received for userid and stowed credentials for that userid were found in the Client Pack Registry.

Action: None; normal operation.

SER8233I userid Login credentials saved

Explanation: A connection request was received for userid and the associated credentials were saved in the Client Pack Registry.

Action: None; normal operation.

SER8234I userid Login credentials deleted

Explanation: A disconnection request was received for userid and stowed credentials for that userid were deleted from the Client Pack Registry.

Action: None; normal operation.

SER8235E userid Failure in saving login credentials

Explanation: A connection request was received for userid and the associated credentials could not be saved in the Client Pack Registry.

Solution: Contact Micro Focus Customer Care.

SER8272E CMN connections temporarily inhibited

Explanation: This message is displayed when an external logon is attempted at ZMF startup when such connections are disallowed while the delay file is being processed. External logons are initiated from batch processes like CMNWRITE, TSO users connecting to ZMF, XML Services requests for ZMF, etc.

Solution: Try the logon again or resubmit the batch process after delay file processing is finished and message CMN_461I is displayed in SERPRINT.

SER8273E Access denied to user {userid}; the maximum number of users of the product ({product}.

Explanation: A user has attempted to access SERNET where the maximum number of users has been reached.

Solution: Retry access after number of users has reduced.

SER8274E Unable to acquire lock table lock during termination of SERNET.

Explanation: Internal use only.

Solution: Contact Micro Focus Customer Care.

SER8275E Abend while processing the lock table - see dump.

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8276E Abend during {function name} function for {userid}; see logrec for details.

Explanation: An abend occurred during the processing of a ’function name’ call to SERLCSEC for the userid specified.

Solution: The abend is typically in RACF code in response to a bad parameter list. Isolate the logrec entry (using ICFEREP) and give the information to Micro Focus Customer Care.

SER8300 SERXMLO

SerNet XML Output Generator. Generate XML from an output DSECT.

SER8300E Response XML not generated because of no XML data space

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8302E No output XML address passed to "Put" in the Xmlo parameter block

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8303E Id "{id}" ({value}) in the Xmlo parameter block is not "XMLO"

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8304E Level number {level} in the Xmlo parameter block is incorrect

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8305E Invalid function "{function}" ({value}) in the Xmlo parameter block

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8306E Residual {code} return code in the Xmlo parameter block

Explanation: Information.

SER8308E No output buffer address passed to "Open" in the Xmlo parameter block

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8309E No output buffer length passed to "Open" in the Xmlo parameter block

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8310E The Xmlo output buffer length {length} is too short, it must be >5K

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8311E No input buffer address passed in the Xmlo parameter block

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8312E No input data passed to "Put" in the Xmlo parameter block

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8313E No output buffer address passed to "Put" in the Xmlo parameter block

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8314E The Xml Put exit buffer length {length} is too short, it must be >5K

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8315E No XML defined for response message "{object} {message} {parameter}"

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8316E Required output exit not passed to SERXMLO

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8317E XML output address parameter precedes the output buffer

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8318E XML output address parameter is beyond the output buffer

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8319E No output buffer length passed to "Put" in the Xmlo parameter block

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8400 SERXMLI

XML Message Input. This program examines an XML document and extracts any tags therein. The tags are recorded in the tag pool.

SER8400E Invalid XML document in message body

Explanation: Internal error.

Solution: Examine the XML request, this is probably a syntax error. Contact Micro Focus Customer Care for further assistance.

SER8401E Invalid XML service combination: Obj={object} Msg={message}

Explanation: Internal error.

Solution: Examine the XML statement, this is probably a syntax error. Contact Micro Focus Customer Care for further assistance.

SER8402E XML value is too long for field {field}

Explanation: Internal error.

Solution: Examine the XML statement, this is probably a syntax error. Contact Micro Focus Customer Care for further assistance.

SER8403E XML dataspace in termination mode

Explanation: Information, the Sernet started task is on its way down.

SER8404E XML dataspace VRM mismatch.

Explanation: The default XMLSPACE has a version, release and modification (VRM) field in the dataspace root record. This must match the VRM of the server. The VRM is displayed at server start up along with the manufacture date/time. See message SER6414I

Solution: Reload the XMLSPACE using the XMLLOAD in the installation JCL.

SER8405EuuuuuuuuService Denied: Service=service Scope=scope Message=message

Explanation: Permission to execute the tendered XML request was denied by security.

Solution: None.

SER8406E </service> string not found at end of XML buffer

Explanation: On inspecting an XML request it was determined that a </service> specification was missing.

Solution: Correct the input XML and resubmit the request.

SER8414W Unrecognized tag in request for user {userid}, tag: {taglist}

Explanation: An unrecognized tag was found in the XML request

Solution: Examine the XML request, correct, and resubmit.

A tag name with incorrect case will cause this warning message.

Another example is a misspelled tag name. Consider the following XML request, where the "appl" TAG has been spelled incorrectly ("applE"). The NETWORK trace for user USER252 has been enabled with a buffersize of 1,024K, and the XML WARNING facility is enabled (value for KEYWORD WARN is YES).

...

    <?xml version="1.0"?>
    <service name="IMPACT">
        <scope name="CMPONENT">
            <message name="LIST">
                <header>
                    <subsys>8</subsys>
                    <product>CMN</product>
                </header>
                <request>
                    <applE>ACTP</applE>
                    <libType>SRS</libType>
                    <component>ACPSRS00</component>
                </request>
            </message>
        </scope>
    </service>

This will generate a message similar to the following:

...

    SER2550T USER252 SERUSER INPUT: Address=1735B014 Length=0168 TCA=1726B000
    SER2551T USER252 0000/00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 *................................*
    SER2551T USER252 0000/0020 Same as above
    SER2551T USER252 0040/00000000 00000000 00000000 00000000 4C6FA794 9340A585 99A28996 957E7FF1 *................<?xml version="1*
    SER2551T USER252 0060/4BF07F6F 6E404CA2 8599A589 83854095 8194857E 7FC9D4D7 C1C3E37F 6E404CA2 *.0"?\> <service name="IMPACT"\> <s*
    SER2551T USER252 0080/83969785 40958194 857E7FC3 D4D7D6D5 C5D5E37F 6E404C94 85A2A281 87854095 *cope name="CMPONENT"\> <message n*
    SER2551T USER252 00A0/8194857E 7FD3C9E2 E37F6E40 4C888581 8485996E 404CA2A4 82A2A8A2 6EF84C61 *ame="LIST"\> <header\> <subsys\>8</*
    SER2551T USER252 00C0/A2A482A2 A8A26E40 4C979996 84A483A3 6EC3D4D5 4C619799 9684A483 A36E404C *subsys\> <product\>CMN</product\> <* 
    SER2551T USER252 00E0/61888581 8485996E 404C9985 98A485A2 A36E404C 81979793 C56EC1C3 E3D74C61 */header\> <request\> <applE\>ACTP</*
    SER2551T USER252 0100/81979793 C56E404C 938982E3 A897856E E2D9E24C 61938982 E3A89785 6E404C83 *applE\> <libType\>SRS</libType\> <c* 
    SER2551T USER252 0120/96949796 958595A3 6EC1C3D7 E2D9E2F0 F04C6183 96949796 958595A3 6E404C61 *omponent\>ACPSRS00</component\> </*
    SER2551T USER252 0140/998598A4 85A2A36E 404C6194 85A2A281 87856E40 4C61A283 9697856E 404C61A2 *request\> </message\> </scope\> </s*
    SER8255T USER252 SERUSER 1726B000 request has last payload FF0307261BD4E944, VmruByts=00007EF4, Vmru\#LDR=00007EF4, VmruT\#LR=00007
    SER8258T USER252 SERUSER 1726B000 routing request XML DATA to application, VCAA1ARQ=1735B000 VCAA1ARS=172BD000
    SER1100T USER252 Storage obtain: TCB=008B7020 PSW=15B5BA8A R0=8100011C, Out: RC=00 R1=17288280 Size=0000011C
    SER1100T USER252 Storage obtain: TCB=008B7020 PSW=0001843C R0=81008000, Out: RC=00 R1=17327000 Size=00008000
    SER1100T USER252 Storage obtain: TCB=008B7020 PSW=00018606 R0=8100003D, Out: RC=00 R1=17288020 Size=0000003D
    SER1100T USER252 Storage obtain: TCB=008B7020 PSW=00018606 R0=8100003F, Out: RC=00 R1=17288210 Size=0000003F
    SER1100T USER252 Storage obtain: TCB=008B7020 PSW=00018606 R0=81000040, Out: RC=00 R1=172883A0 Size=00000040
    SER1100T USER252 Storage obtain: TCB=008B7020 PSW=00018606 R0=8100003F, Out: RC=00 R1=17288400 Size=0000003F
    SER1100T USER252 Storage obtain: TCB=008B7020 PSW=00018606 R0=81000044, Out: RC=00 R1=17288440 Size=00000044
    SER8410T USER252 SERXMLI Request: Prod=CMN Obj=IMPACT Msg=LIST Parm=CMPONENT
    SER8411T USER252 SERXMLI Receive after conversion: Address=1735B064 Length=0053 
    SER8412T USER252 SERXMLI 0...4...8...C...10..4...8...C...20..4...8...C...30..4...8...C...
    SER8413T USER252 SERXMLI 0000 0053 SRSACPSRS00 name="CMPO
    SER8414W Unrecognized tag in request for user USER252, tag: applE, service: IMPACT, scope: CMPONENT, message: LIST

...

SER8500 SERVAMH

SerNet API Message Handler. This only purpose is to call the correct module. There is no more reformatting of the input request. It is taken "as is" and this module does all of the required work in the VCA$.... areas. No extra storage is consumed.

SER8500E *Error* Service module not found for: {sernet-task}

Explanation: The "product" in the XML request is probably wrong, for example it may be CMN when it should be XCH.

Solution: Correct the "product" and re-submit.

SER8600 SERXMSIP

Cross Memory Services, SER#PARM duties:

  • XMS - Cross Memory Services on SerNet STC side.
  • Manipulation of //SER#PARM PDS for member updates, additions;
  • reading to determine TCP/IP addresses from SERCLIEN side.
  • Creation/deletion of new address spaces.

SER8600E Unable to open //SER#PARM; connection refused

Explanation: Check the spelling for DDNAME SER#PARM.

Solution: Correct and re-submit.

SER8601E SERXMSIP Abend 325; Reason code={code}

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8602E Cannot find requested subsystem {subsys}; member {member}

Explanation: Check the spelling of member.

Solution: Correct and re-submit.

SER8603I XMS - Cross Memory Services active

Explanation: Information.

SER8604I ****** This is member "#SER{memsuffix}" created {when} ****

Explanation: Information.

SER8605I * The purpose of this member is to track the relationship

Explanation: Information.

SER8606I * between this SerNet subsystem, applications and associated

Explanation: Information.

SER8607I * TCP/IP dotted decimal address && port number.

Explanation: Information.

SER8608I * The member is created/updated by SERVER/SERXMSIP as needed.

Explanation: Information.

Explanation: Information.

SER8610I * <== asterisk in column one denotes comment.

Explanation: Information.

SER8611I * SMF-ID (SMFI) uniquely identifies the LPAR. Multiple APPs possible.

Explanation: Information.

SER8612I * SMFI.SUBS APP DOT.TED.DEC.MAL PORT# TCPIPROC --Update-Time-Stamp--

Explanation: Information.

SER8613I *- Settings at creation above -*

Explanation: Information.

SER8614I * END OF DATA

Explanation: Information.

SER8615I CMN TCPIP information not detected - cannot be saved.

Explanation: Information.

SER8650 SERBUILD

(former CDFBUILD) Build and manipulate eight files database

SER8650I LEGEND - Type of Changes Symbols:

Explanation: Information.

SER8651I Common base 012345 relative Base record number

Explanation: Information.

SER8652I Deleted base < _B__ deleted Base record in version B

Explanation: Information.

SER8653I Replaced base < 2345 replaced Base record; see next

Explanation: Information.

SER8654I Replacement <>__C_ replacing record in version C

Explanation: Information.

SER8654I Replacement <>__C_ replacing record in version C

Explanation: Information.

SER8655I Inserted line > AB__ inserted line in versions A and B

Explanation: Information.

SER8656I Cut Base line <<___D cut (moved around) Base line in version D

Explanation: Information.

SER8657I Pasted Base line >>___D pasted (moved around) Base line in version D

Explanation: Information.

SER8658I User deleted /*3456 user deleted Base record

Explanation: Information.

SER8659I User deleted /*_B__ user deleted line of version B

Explanation: Informaton.

SER8660I User overtyped ><___+ user overtyped line

Explanation: Information.

SER8661I User deleted /*_B__ user deleted line of version B

Explanation: Information.

SER8662I User inserted > ___+ user inserted line

Explanation: Information.

SER8663I User cut <<3456 user cut Base record

Explanation: Information.

SER8664I User cut <<__C_ user cut line of version C

Explanation: Information.

SER8665I User pasted >>___+ user pasted line

Explanation: Information.

SER8700 SERXMVS

SerNet MVS-MVS Processor

SER8700I Transfer scheduled for transmission

Explanation: Information.

SER8701I Transfer completed successfully

Explanation: Information.

SER8702I {integer1} of {integer2} members copied successfully

Explanation: Information.

SER8703I Transfer completed successfully with warnings

Explanation: Information.

SER8704I At least one member excluded - superset-subset

Explanation: Information.

SER8705E Source data set migrated to tape

Explanation: An MVS2MVS request specified an input dataset name that was on migration level-2.

Solution: Recall the specified dataset name and resubmit the request.

SER8706E Target data set migrated to tape

Explanation: An MVS2MVS request specified an output dataset name that was on migration level-2.

Solution: Recall the specified dataset name and resubmit the request.

SER8712I Error Sending data to partner

Explanation: Information, see related SER87nna messages.

SER8716E Error - Target Dataset not found

Explanation: Information.

Solution: Determine if the target dataset exists.

SER8717E Error - Member provided for sequential dataset

Explanation: Information.

Solution: Probable user error, is this the correct dataset? Remove member name if this is the correct dataset.

SER8718E Error - Dataset organization not supported'

Explanation: Probable user error.

Solution: Verify the dataset names are correct.

SER8719E Error - Target Member cannot contain wildcard

Explanation: The target dataset needs a real member name, not a wildcard.

Solution: Specify a real member name for the target dataset.

SER8720E Error - DSORG conversion not supported

Explanation: DSORGs must be the same.

SER8721E Error - Member required for SEQ/PDS copy

Explanation: Missing member name.

Solution: Supply a member name.

SER8722E Error - Request is not supported

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8724E Error - Unable to obtain target information

Explanation: Probable user error.

Solution: Verify the target dataset exists, and is the correct dataset.

SER8725E Error - Unable to obtain source attributes

Explanation: Probable user error.

Solution: Verify the source dataset exists, and is the correct dataset.

SER8726E Error - Source Dataset not found

Explanation: Probable user error.

Solution: Correct the name of the source dataset.

SER8727E Error - Actual Source DSORG does not match specified DSORG

Explanation: Probable user error.

Solution: Examine user input and the dataset in question.

SER8728E Error - Actual Target DSORG does not match specified DSORG

Explanation: Probable user error.

Solution: Examine user input and the dataset in question.

SER8729E Error - Unable to allocate dataset; DSORG mismatch

Explanation: Probable user error.

Solution: Examine user input and correct.

SER8730E Error - Unable to allocate dataset; Source DSORG must be SEQ or PDS

Explanation: Information.

Solution: Examine user input, correct and re-submit.

SER8732E Error - Unable to obtain enqueue on SYSPRINT

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8733E Error - IEBCOPY failed; RC={return code} Reason={reason code}

Explanation: Information.

Solution: Record return code and reason code, examine SYSLOG and the SERNET STC JES2 datasets for related messages. Contact Micro Focus Customer Care.

SER8734E Error - Unable to obtain unload data set attributes

Explanation: Probable user error.

Solution: Verify the existence of the data set in question. Is this the correct dataset?

SER8740E Error - Data set allocation failed

Explanation: Probable user error.

Solution: Examine user input and correct.

SER8741E Address space creation failed

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care.

SER8800 SERMMWD

MailMan watchdog This task is attached by the server at start up time. The purpose of this module is to read the MailIni file, record the IP address and port for MailMan, and keep an eye on the link to MailMan by pinging the IP-address and port periodically.

SER8805E Unable to open MAILINI file

Explanation: An open of the MAILINI failed.

Solution: If MAILMAN support is required ensure a valid DD card for the MAILINI file is specified in the JCL for the STC.

SER8806E Syntax: mailini-content

Explanation: The content of the MAILINI file is unacceptable.

Solution: If MAILMAN support is required correct the content of the MAILINI file and restart the STC.

SER8850 SERSCAN

Scan for particular character string(s) within data set/member(s). Service requests come in from all directions but work is accomplished in started task.

SER8850E RECFM=U Disallowed

Explanation: An attempt was made to scan a load library; this is not supported.

Solution: If necessary, reissue the scan request against a dataset which is not a load library.

SER8851E Cannot scan Load library (Undefined record format)

Explanation: An attempt was made to scan a load library; this is not supported.

Solution: If necessary, reissue the scan request against a dataset which is not a load library.

SER8852E SERSCAN/SERXFLIO Error

Explanation: An internal call to the SERXFLIO module incurred an error.

Solution: Report this error to Micro Focus Technical Support.

Back to top