It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×5,997
×77

question asked: Sep 19 '18, 3:16 p.m.
question was seen: 1,681 times
last updated: Sep 28 '18, 3:25 p.m.

Related questions

FAQ - How this Forum works

I am getting JzosUtility.executeCommand errors - EDC5045I The operation attempted could not be performed because the file was open. Is there a missing pre-req?

0
Janet Masters (17●8●14) | asked Sep 19 '18, 3:16 p.m.
Recently migrated to RTC 6.0.6, and upgraded the Buildsystem Buildtoolkit to v6.0.6, and started getting JzosUtility.executeCommand errors - EDC5045I The operation attempted could not be performed because the file was open.  Is there a missing pre-req? 

This feels like a new problem introduced with the upgraded toolkit:

2018-09-19 08:45:14: JzosUtility.executeCommand: alloc fi(ZEE00737) da('TDAPM.GM610KL.LINK(AGMATM64)') shr msg(1)
2018-09-19 08:45:14: JzosUtility.executeCommand: alloc fi(ZEE00738) da('TDAPM.GM610KL.LINK(AGMZDUMP)') shr msg(1)
2018-09-19 08:45:14: JzosUtility.executeCommand: alloc fi(ZEE00739) da('TDAPM.GM610KL.AAGMINST(AGMJ5REC)') shr msg(1)
2018-09-19 08:45:14: JzosUtility.executeCommand: alloc fi(ZEE00740) da('TDAPM.GM610KL.AAGMINST(AGMJ7ACC)') shr msg(1)
2018-09-19 08:45:14: JzosUtility.executeCommand: alloc fi(ZEE00741) da('TDAPM.GM610KL.AAGMINST(AGMJ3ALO)') shr msg(1)
2018-09-19 08:45:14: JzosUtility.executeCommand: alloc fi(ZEE00742) da('TDAPM.GM610KL.AAGMINST(AGMJ6APP)') shr msg(1)
2018-09-19 08:45:15: JzosUtility.executeCommand: free fi(ZEE00719) msg(1)
2018-09-19 08:45:15: Update(save) ISPF statistics for TDAPM.GM610KL.C(AGMAKFKA)
2018-09-19 08:45:15: JzosUtility.executeCommand: alloc fi(ZEE00743) da('TDAPM.GM610KL.LINK(AGMZ$WTO)') shr msg(1)
2018-09-19 08:45:15: JzosUtility.executeCommand: alloc fi(ZEE00744) da('TDAPM.GM610KL.LINK(AGMALOG)') shr msg(1)
2018-09-19 08:45:15: JzosUtility.executeCommand: alloc fi(ZEE00745) da('TDAPM.GM610KL.LINK(AGMZXZAP)') shr msg(1)
2018-09-19 08:45:15: JzosUtility.executeCommand: alloc fi(ZEE00746) da('TDAPM.GM610KL.LINK(AGMATJAV)') shr msg(1)
2018-09-19 08:45:15: Update(save) ISPF statistics for TDAPM.GM610KL.C(AGMALOG)
2018-09-19 08:45:15: JzosUtility.executeCommand: FREE fi(ZEE00735) msg(1)
2018-09-19 08:45:15: JzosUtility.executeCommand: free fi(ZEE00720) msg(1)
2018-09-19 08:45:15: JzosUtility.executeCommand: alloc fi(ZEE00747) da(TDAPM.GM610KL.CJSRC) SHR REUSE msg(1)
2018-09-19 08:45:15: JzosUtility.executeCommand: alloc fi(ZEE00748) da('TDAPM.GM610KL.LINK(AGMAPI31)') shr msg(1)
2018-09-19 08:45:15: Remove TDAPM.GM610KL.CJSRC(AGMATEMS)
2018-09-19 08:45:15: JzosUtility.executeCommand: free fi(ZEE00722) msg(1)
2018-09-19 08:45:15: //DD:ZEE00739: fopen() failed; EDC5045I The operation attempted could not be performed because the file was open.; errno=45 errno2=0xc00b0445 last_op=43 errorCode=0x0
2018-09-19 08:45:15: JzosUtility.executeCommand: free fi(ZEE00739) msg(1)
2018-09-19 08:45:15: JzosUtility.executeCommand: free fi(ZEE00723) msg(1)

3 answers

Most liked answers|Newest answers|Oldest answers ↑

0
permanent link
Kenny Smith (302●5●13) | answered Sep 25 '18, 9:28 a.m.

 In ISPF, can you see if anyone has the member open or have you already confirmed that? Is it a member you can delete and retry?

Comments
Janet Masters commented Sep 27 '18, 9:49 a.m.

No, the only files open would be the ones being touched by the build.  I understand that there is a problem with the multi-threading function provided in RTC EE v6.0.6.

0
permanent link
Kenny Smith (302●5●13) | answered Sep 28 '18, 9:46 a.m.

When you upgraded the build system toolkit, did you do a full SMP/e install of the 6.0.6 parts? You need both the build toolkit and the build agent (separate FMIDs).


Also, what JDK are you using on z/OS?

Comments
Janet Masters commented Sep 28 '18, 10:27 a.m.
The system support group installed three FMIDs:  HRCC606, HRBA606, HRBT606.  And used BLZJAVA = '/java/J6.0_64'. 

When I started the agent, I used 'export JAVA_HOME=/Java/J7.1_64'.  Is that a problem?  I did check to make sure J7.1_64 was available on the system.
0
permanent link
Janet Masters (17●8●14) | answered Sep 28 '18, 3:25 p.m.

We received a replacement jar file from RTC EE Support, and that seems to have fixed the problem.  Thanks!

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.