I created an assembler import file using DMHBALA from RAASync and copied it down to our RAA server after removing RAASync control cards. RAA is version 126.96.36.199 and is installed on a Windows server. When using Collect Inventory to load the import file, the Analyze File step is queued during Postprocessing. This step fails and the imported data is backed out. The failure appears to be an error when attempting to access the mainframe PDS for the file. If I manually skip this step, everything appears to be okay. I haven't set up the mainframe communications yet, but my question is why is the Analyze File step queued and why does it need access to the mainframe file during Postprocessing since it is an import file? Thanks.
Re: ASM Import File Failure During Analyze File2013-11-07T16:50:33ZThis is the accepted answer. This is the accepted answer.
Attached are the logs. I'm assuming the Postprocessor is attempting a mainframe connection in that the logs indicate the file is gone. Import entries are in RAA until the Analzye File queue is run which removes them.
In experimenting, I put the source in a local folder and pointed the LIBR card to this location. Analyze File did not indicate the file was gone and the import entries remained, even though not all correct. But, this further suggests that Analzye File is looking for the source.
Attached are logs. They contain only the new entries from the latest test performed for this reply.
boyerpl 100000SWES235 Posts
Re: ASM Import File Failure During Analyze File2013-11-07T19:16:04ZThis is the accepted answer. This is the accepted answer.
- MiklP 270005K6G2
This sounds like a problem that was fixed in V188.8.131.52. See https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014906828&ps=100
- Loading any import file for an Assembler program results in LANGUAGE_CD='GONE' (37353)
You'll need to move at least to V184.108.40.206 to correct that, but I would suggest getting on V220.127.116.11 so you have all the other fixes and enhancements that have occurred since V18.104.22.168.