Skip to main content
Version: 23.1

IBM i LSAM Messages

Table of Job Completion Messages

This table documents error messages produced by the SMA File Transfer programs. These are sometimes reported in an IBM i job log and/or sent to the OpCon user interface as "Detailed Job Messages."

Message IDSevMeaning
SFT00010Unable to open conversion table CD in SMAFTSR10 or SMAFTAR10
SFT000240Destination data type not specified or not recognized; see SMAFT logs
SFT000340Source data type not specified or not recognized; see SMAFT logs
SFT000540iConv_2: converted text data length is zero
SFT009940SMAFT EOJ ERROR LOG: &1
SFT10010Invalid file name
SFT10020File does not exist
SFT10030Unsupported file
SFT10040Unknown user
SFT10050Security error
SFT10060File access error
SFT10990Invalid request

The table below presents LSAM status messages forwarded to the SAM. The message descriptions are displayed in Operations in the OpCon User Interface following the job status.

StatusReturn CodeMeaning
0SMA0030Job not found
1SMA0001Job Description in run request is invalid
1SMA0002Job Queue in run request is invalid
1SMA0003Job Output Queue in run request is invalid
1SMA0004(a)User ID in run request is invalid
1SMA0004(b)SBMDBFCMD failed, unable to complete user authority check
1SMA0004(c)SBMDBFCMD failed, user not authorized to command
1SMA0005Current Library in run request is invalid
1SMA0006Job name is invalid. It should be alpha-numeric
1SMA0007Job subsystem name cannot be determined
1SMA0008Job Queue is held, job cannot run until queue is released
1SMA0020Pre-run image in run request is invalid
1SMA0021Run image in run request is blank
1SMA0022Run image in run request is invalid (failed IBM i CMDCHK)
1SMA0023Run job submission failed
1SMA0024Job initial library list is invalid
1SMA0025Unrecognized job type in OpCon job start request (TX1)
1SMA0027FTP job user profile or password invalid
1SMA0028FTP job sub-command source member file error
1SMA0029FTP job invalid action type
1SMA0042FTP job remote system name not supplied
1SMA0044Tracked or Queued Job start request did not include Private Data with Job ID
1SMA0045LSAM cannot find Job Tracking record for Tracked/Queued Job start request
1SMA0052Tracked/Queued Job already released or cancelled by IBM i Operator
1SMA0062OpCon transaction XML field code is invalid
1SMA0067SMAFT job request received with no source IP address
1SMA0073Job auxiliary data in XML fields is invalid, job request rejected
1SMA0108Operator Replay failed: Invalid script name, not on file
2SMA0010Maximum number of jobs in system exceeded
3ACTIVEPre-run job is active, response to Type 2 message
3ACTIVE HELDPre-run job is active but held, response to Type 2 message
3SMA0033Pre-run job is active
3SMA0040Pre-run job is active - $JOB:KILL command failed
4SMA0034Pre-run job error
4SMA0096Pre-run job already ended – job not found for Kill request
4SMA0098Pre-run ended by user request ($JOB:KILL)
5MSGW-Active job in Message Waiting status, message text follows
5ACTIVERun job is active, response to Type 2 message
5ACTIVE HELDRun job is active but held, response to Type 2 message
5SMA0031Job waiting to run
5SMA0035Run job is active
5SMA0041Run job is active - $JOB:KILL command failed
5SMA0246IBM i job completed normally, now running post-procedure SCANSPLF
6SMA0036Run job is complete
6SMA0100Operator Replay job completed OK
7SMA0037Run job is error
7SMA0064SMAFT Server get-file (IFS files) program SMAFTSR10 failed
7SMA0065SMAFT Server get-file (IBM i save files) program SMAFTSR20 failed
7SMA0066SMAFT Server get-file (DB2 files) program SMAFTSR30 failed
7SMA0074SMAFT Agent unable to find transfer job index master record
7SMA0075SMAFT Agent job did not find any transfer task definition fields
7SMA0076SMAFT Agent job found invalid XML field code in job parameters file
7SMA0077SMAFT Agent job detected a failure of the XML parser module
7SMA0078SMA File Transfer job failed – refer to OpCon job properties for details
7SMA0079SMA File Transfer encryption or compression option not supported
7SMA0080SMA File Transfer Destination file exists and option is do not overwrite
7SMA0081SMAFT Agent put-file (IFS files) program SMAFTAR10 failed
7SMA0082SMAFT Agent put-file (IBM i save files) program SMAFTAR20 failed
7SMA0083SMAFT Agent put-file (DB2 files) program SMAFTAR30 failed
7SMA0084SMAFT: IFS file type is invalid, only type STFM (stream file) is supported
7SMA0085SMAFT value supplied for "If File Exists" parameter is not recognized
7SMA0086SMAFT Agent cancels transfer request because file exists and option is do not overwrite
7SMA0087SMAFT Agent failed during attempt to backup target file
7SMA0088SMAFT Agent detected invalid character in record separator following hex escape sequence
7SMA0089SMAFT Agent detected invalid character in record separator following octal escape sequence
7SMA0090SMAFT Agent detected invalid character in record separator following an escape character
7SMA0091SMAFT Agent detected invalid hexadecimal number value in record separator
7SMA0092SMAFT Agent detected invalid octal number value in record separator
7SMA0093SMAFT Agent detected invalid character number in record separator
7SMA0094SMAFT Agent unable to clear target file that is subject to overwrite
7SMA0095SMAFT Agent failed during creation of target file that did not exist
7SMA0097Job run command has already ended – job not found for Kill request
7SMA0099Run job ended by user request ($JOB:KILL)
7SMA0101Operator Replay failed: Telnet host not recognized (getHostByName)
7SMA0102Operator Replay failed: Cannot open socket to use with telnet (sock)
7SMA0103Operator Replay failed: Cannot connect to telnet service (connect)
7SMA0104Operator Replay failed: Failed to set socket attributes for telnet session (fcntl)
7SMA0105Operator Replay failed: Bell character received = typed (Send) value error
7SMA0106Operator Replay failed: Replay script timeout
7SMA0107Operator Replay failed: Error in script control definitions
7SMA0109Operator Replay failed: Script has no sequence records
7SMA010AOperator Replay failed: Technical failure at startup, see driver job log
7SMA010BOperator Replay failed: STROPRRPY command incorrect DEVICE or IPADDR
7SMA010COperator Replay failed: OpCon job master not found
7SMA010DOperator Replay failed: Script user not provided to driver program
7SMA010EOperator Replay failed: Dynamic Variable replacement error, see Script log
7SMA010FOperator Replay failed: SMAFAILJOB command in response rules, or general failure - see program dump report and driver job log
7SMA0135SMAFT Agent failed to grant authority to new backup file in SMABAK library
7SMA0136SMAFT Agent detected non-numeric record length in pre-pended data before first received data record
7SMA0137SMAFT Agent detected non-numeric record length embedded between variable records in received data
7SMA0138SMAFT Agent unable to delete old backup copy of save file in SMABAK library
7SMA0140SMAFT Agent detected data record length not equal file record length
7SMA0141SMAFT Agent timer expired waiting for transaction accomplishment
7SMA0142SMAFT Agent reports general error – refer to job log
7SMA0143SMAFT Agent communications idle time exceeded – lost connection?
7SMA0144SMAFT Server timer expired waiting for transaction accomplishment
7SMA0145SMAFT Server reports general error – refer to job log
7SMA0146SMAFT Server communications idle time exceeded – lost connection?
7SMA0224Captured job ID not found in Call string
7SMA0225Specified dynamic variable name not found in LSAM master file
7SMA0226Requested dynamic variable operation is not V or L, or LDA key is blank
7SMA0227Dynamic variable type in LSAM master file is not V when operation V requested
7SMA0228Dynamic variable separator characters not found in LSAM control file
7SMA0229User-defined program for dynamic variable value failed
7SMA0247SCANSPLF command requested but not found for post-process job evaluation (typically an LSAM internal programming error) - requires SMA Support to resolve
7SMA0249IBM i job completed normally, but post-processing SCANSPLF reports error
8SMA0018(LSAM internal job status: Pre-run job completed normally)
9SMA0038Job completed with no error
9SMA0039Job completed with status not equal 0

Table of Return Codes

These return codes are sent from the IBM i Agent to the OpCon server. Although these codes are for OpCon product internal use, they are useful for understanding the implication of the various job completion Message IDs in the table above.

ValueShort DescriptionLong Description
NGLBSTS = S Job pre-start DefinitionThis is an internal status for the LSAM, applied to the initial job status master file as the skeleton profile record is first established. There should always be SAM key fields on this record, but no indication of Pre-run or Main Call command.
0Job not foundThis status indicates that the job in question is not currently executing on the specified machine. This could occur in response to a Job Status request. The SAM will treat this as an error termination if the job was in a running status; otherwise, if the job is still in a Start Attempted status, the SAM will resend TX1 (job start reqeust) for the job.
1Job Initiation ErrorThis status indicates that an error has occurred which prevents the job in question from being initiated. The Scheduling System will post an error message describing the error, and the job will be treated as a failed job, including the processing of Event records. Examples of the kind of errors which require this status response are:
+ Prerun Image Not Found
+ Job Start Image Not Found
+ Security Check Failure
+ Invalid User ID, etc.
The specific errors will vary form machine to machine, and the Scheduling System will post whatever message is returned in the Platform-Specific Completion Code. This type of error typically requires some action to be taken to correct the error condition.
2Job to be Re-QueuedThis status indicates that some temporary condition exists which prevents this job from being executed at this time. The Scheduling System may post a message describing the condition, and will reschedule the job. This type of error typically does not require any action to be taken to correct the condition that necessitated the re-queuing, other than attempting to restart the job. The specific errors will vary from machine to machine, and the Scheduling System will post whatever message is returned in the Platform-Specific Completion Code.
3Prerun Active
4Prerun Failed
5Job Running
6Job Finished OK, Completion Notice Pending
7Job Errored, Completion Notice Pending
8Job finished OK, closed in tracking file
9Job errored, closed in tracking file