OS4X Core - list of returncodes
os4xeq
- 0: everything OK or help was displayed
- 1: configfile /etc/os4x.conf not readable
- 2: config from database not readable
- 3: no parameters given
- 4: problem with file (take a look at the output of the program)
- 5: partner not found
- 6: unknown OFTP version
- 7: error in signing data (refer to output and/or send log)
- 8: error in compressing data (refer to output and/or send log)
- 9: error in encrypting data (refer to output and/or send log)
- 10: file size after signing and/or compressing and/or encrypting is zero
- 11: error during adding file to send queue
- 12: no file parameter given when enqueueing OFTP2 EERP/NERP
- 13: improper usage of sign flag
- 14: undefined cipher suite for EERP
- 15: hashing error during OFTP2 operation
- 16: invalid 'V' file with format MVS
- 17: invalid virtual filename
- 18: entry exists, aborting is requested for such a case
os4xped
- 0: everything OK
- 1: no parameters given
- 2: help was displayed
- 3: no shortname given
- 4: configfile /etc/os4x.conf not readable
- 5: config from database not readable
- 6: illegal value for connection type
- 7: error searching for partner with given shortname (SQL query problem, check syslog)
- 8: more than one entry for shortname found (check database scheme)
os4xpoll
- 0: everything OK or help was displayed
- 1: no shortname given or no partner for given shortname found
- 2: configfile /etc/os4x.conf not readable
- 3: config from database not readable
- 4: fork error (process table full?)
- 5: setsid() problem (cannot daemonize)
- 6: license invalid
- 7: OFTP2 not supported in this version
If the „do not daemonize“-option is used (i.e. for checking if any file has been transmitted, if the connect was successful etc.), the following values are returned:
- 11: problem finding partner index in partner table
- 12: connect problem (any type, please refer to the logs to obtain more information)
- 13: error in OFTP2 secure authentification (available since OS4X build 2020-08-26)
- 15-: sum of transfered and/or acknowledged files in the successfully initiated OFTP session.
Because returncodes may have a value of 0-255, a restriction was done here: The returncode consists of two components: 10 + (5+transfered files)%240. For most situation this will be enough, but look at some examples:
2 files transfered: rc = 10+(5+2)%240 = 17
500 files transfered: rc = 10+(5+500)%240 = 35
1234 files transfered: rc = 10+(5+1234)%240 = 49
os4xrd
- 0: everything OK or help was displayed
- 1: configfile /etc/os4x.conf not readable
- 2: config from database not readable
- 3: license invalid
- 4: existing receive daemon found in database (please cleanup)
- 5: fork error (process table full?)
- 6: setsid() problem (cannot daemonize)
- 7: fork error (process table full?) for network server
- 8: fork error (process table full?) for Brick server
- 9: network socket error
- 10: network bind error
- 11: network listen error
os4xsqd
- 0: everything OK or help was displayed
- 1: configfile /etc/os4x.conf not readable
- 2: config from database not readable
- 3: existing send queue daemon found in database (please cleanup)
- 4: fork error (process table full?)
- 5: setsid() problem (cannot daemonize)
- 6: license invalid
os4xsend
- 1: configfile /etc/os4x.conf not readable
- 2: config from database not readable
- 3: setsid() problem (cannot daemonize)
- 4: problem with file (take a look at the output of the program)
- 5: fork error (process table full?)
- 6: unknown OFTP version
- 7: error in signing data (refer to output and/or send log)
- 8: error in compressing data (refer to output and/or send log)
- 9: error in encrypting data (refer to output and/or send log)
- 10: file size after signing and/or compressing and/or encrypting is zero
- 11: partner not found
- 12: license invalid
- 13: OFTP2 not supported