Which could be possible reasons for error while unzipping

[demecarv]

Someone much more experience in Unix than me created a JCL Job which basically calls certain very simple jython. In this jython there is a simple call to wsadmin.sh in order to deploy a simple ear file. It was happening successfuly until someone upgraded Websphere from 7 to 8.5. I checked everything related to the Websphere deployment process and as far as I can see, the jython script it is correct. I mean, the jython just had to be changed from WebSphere 7 to WebSphere 8.5 folder and it is correct. Additionally, in order to deploy step-by-step manually, I did "wsadmin>AdminApp.installInteractive('/WebSphereDevelopment/MYAPP/MyAppEAR.ear')" and I get the same error either by using the scripts or "installInteractive" command. The error happens while trying to unzip the ear file. I did chmod 777 to the ear file. Although, it might seem a question related to websphere, I guess it might exist some thing I have to check related to Unix and I have no idea what I have to check. So, my straight question is: which are the common or known possible reasons that usually blocks an application to unzip a file to a temporary folder?
P.S. I apologise to paste the screens separated below. I don't know how to get the entire screen when it is divided in more that one.

Open MVS shell:

Code: Select all

wsadmin>AdminApp.installInteractive('/WebSphereDevelopment/MYAPP/MyAppEAR.ear')
WASX7015E: Exception running command: "AdminApp.installInteractive('/WebSphereDe
velopment/MYAPP/MyAppEAR.ear')"; exception information:
com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.
websphere.management.application.client.AppDeploymentException: ÝRoot exception
is java.lang.RuntimeException: Deploying /WebSphere/was85/dtl85cel/ledm85nd/Dep
loymentManager/profiles/default/temp/app1531162275061662369.ear failed.¨
java.lang.RuntimeException: java.lang.RuntimeException: Deploying /WebSphere/was
85/dtl85cel/ledm85nd/DeploymentManager/profiles/default/temp/app1531162275061662
369.ear failed.
wsadmin>

wsadmin.traceout:

Code: Select all

first screen
000136,Caused by: java.util.zip.ZipException: error in opening zip file
000137,,at java.util.zip.ZipFile.open(Native Method)
000138,,at java.util.zip.ZipFile.(ZipFile.java:231)
000139,,at java.util.zip.ZipFile.(ZipFile.java:161)
000140,,at java.util.zip.ZipFile.(ZipFile.java:132)
000141,,at com.ibm.ws.sip.application.frameworkext.SarToEarConverterTask.isConv
000142,,... 63 more
000143,
000144,Ý11/9/15 13:23:17:594 CST¨ 00000001 AbstractShell A WASX7093I: Issuing
000145,com.ibm.websphere.management.application.client.AppDeploymentException:
000146,java.lang.RuntimeException: java.lang.RuntimeException: Deploying /WebSp
000147,"

first right screen:
000144, message: "WASX7015E: Exception running command: "AdminApp.installIntera
000145,com.ibm.websphere.management.application.client.AppDeploymentException:
000146,here/was85/dtl85cel/ledm85nd/DeploymentManager/profiles/default/temp/app

Second right screen:
000144,ctive('/WebSphereDevelopment/MYAPP/MyAppEAR.ear')"; exception information:
000145, ÝRoot exception is java.lang.RuntimeException: Deploying /WebSphere/was
000146,1531162275061662369.ear failed.

Third right screen:
000144,
000145,85/dtl85cel/ledm85nd/DeploymentManager/profiles/default/temp/app15311622
000146,

Fourth right screen:
000144,
000145,75061662369.ear failed.¨
000146,

[William Collins]

Well, just from the title, failure to put on underpants in the morning.

Seriously, and without looking, it could be an ASCII/EBCDIC issue.

[demecarv]

William, with this possibility in mind ("it could be an ASCII/EBCDIC issue"). Is there a way to check this? I generated the ear file in my Windows machine. Then I copied such ear file from my local machine to z/OS300 via Open Text Connectivity version 14.04 using FTP feature. Is there an Unix command which I could verify what is the ear file format? Supposing so, what is the correct expected during unzip process?

[Robert Sample]

When you copied the file, did you copy as text or binary? A zip file MUST be copied as binary as translating it from ASCII to EBCDIC (the default text transfer when using FTP to a mainframe) will corrupt the zip file.

[demecarv]

Robert, we say in Brazil "gol de placa". In portuguese it means a very beatiful gol in a soccer game under a dificult moment. Thanks! I am transfering the ear file from my windows machine to mainframe via Open Text FTP feature and, in my configurations, it was set up to Auto-Select. There are two file formats allowed: Binary and ASCII. Probably, autoselect was setting to ASCII. The correct is Binary.