We are going to use the pipeline plugin with build nodes running under z/OS Unix System Services (USS). Unfortunately, the sh step does not work out of the box on that platform because (text) files are encoded by default in IBM1047 (some EBCDIC variant) but the implementation within the durable-task-plugin seems to assume implicitly that the shell input and output is in UTF-8 or ASCII based.

First experiments on top of durable-task-1.10 adding character set conversion in BourneShellScript and FileMonitoringTask to any read/write of files script.sh, pid, jenkins-result.txt and jenkins-log.txt were promising.

Update : - the Script.sh file is untagged in z/OS USS , if its tagged as ASCII the script can be executed in z/OS USS. when the script is pushed it need to be tagged as ASCII.