CEA TSO launcher called function: CEA_TSO_START, returned reason code: 0x1013, diagnostic codes: 0x26, 0x0, 0x0, 0x0

zowe / zowe-cli

Zowe CLI

Eclipse Public License 2.0

116 stars 85 forks source link

CEA TSO launcher called function: CEA_TSO_START, returned reason code: 0x1013, diagnostic codes: 0x26, 0x0, 0x0, 0x0 #1021

Closed TimMSbg closed 4 months ago

TimMSbg commented 3 years ago

Hi, when using a TSO profile with codepage --cp 1141 option we get the following error message on rexx execution

CEA TSO launcher called function: CEA_TSO_START, returned reason code: 0x1013, diagnostic codes: 0x26, 0x0, 0x0, 0x0

In z/osmf I can find the this

[tx0000000000000BE8:frztm@atrvss64-c2.rbgs.net (POST) /zosmf/tsoApp/tso?acct=SYPRO&proc=TSOZOWE&chset=697&cpage=1141&rows=24&cols=80&rsize=4096] 2021-06-01T10:32:25.151Z|00005F12|com.ibm.zoszmf.util.tso.CeaException|throwException SEVERE:IZUG1120E: An error occurred. The common event adapter (CEA) component returned reason code 0x1013 and diagnostic codes 0x26, 0x0, 0x0, 0x0.

Command for tso profile: zowe profiles create tso entw-tso -a SYPRO -l TSOZOWE --cp 1141 Command for rexx execution: zowe tso issue command "exec 'LRVD.ITM.REXX(HELLO)'" --ssm --zosmf-p entw-zosmf --tso-p entw-tso

Is it possible to always use the right ceatso_request.ceatso_charset and ceatso_request.ceatso_codepage when executing rexx procedures?

Thanks and regards Tim

t1m0thyj commented 3 years ago

Is it possible to always use the right ceatso_request.ceatso_charset and ceatso_request.ceatso_codepage when executing rexx procedures?

We need to determine where the issue originates - in z/OSMF APIs or in Zowe CLI. To do this, I can provide a script that would call z/OSMF APIs directly that you could test. Are you able to run Bash scripts at your site?

TimMSbg commented 3 years ago

Hello t1m0thyj, sorry for coming back to you so lately. Yes, I'm able to run a bash script on my site. Please send it to me.

t1m0thyj commented 3 years ago

@TimMSbg Here's a link to the Bash script: https://gist.github.com/t1m0thyj/f748e1d87f1c7cc34b32655dd4ad5ac6#file-test-sh

Before running it, you'll need to update the values of constants defined at the top for your site:

CURL_ARGS - Arguments that get passed on to curl which you can likely leave unchanged. The --insecure argument behaves the same as --reject-unauthorized false on a Zowe CLI profile.
PY3 - Name of Python 3 binary on your machine (likely python or python3)
TSO_CMD - Your z/OS TSO command (likely exec 'LRVD.ITM.REXX(HELLO)' based on your example above)
TSO_PARMS - Your z/OS TSO session parameters (likely acct=SYPRO&proc=TSOZOWE&chset=697&cpage=1141&rows=24&cols=80&rsize=4096 based on your example above)
ZOSMF_HOST - Host name of z/OSMF service running on mainframe LPAR
ZOSMF_PORT - Port number of z/OSMF service
ZOSMF_USER - User name to connect to z/OSMF service

Please let us know if the error persists when running this script.

TimMSbg commented 3 years ago

@t1m0thyj there was no error running this script.

github-actions[bot] commented 2 years ago

Thank you for creating a bug report. If you haven't already, please ensure you have provided steps to reproduce it and as much context as possible.

adam-wolfe commented 4 months ago

Closing this issue due to inactivity.