Need help launching AS400 recorded macros Using VBA with PCOMM "StartMacro" Function

Pretty sure the internal macro language for IBM I Access for Windows is VBA.  Been a while but when recording a macro I recapp there are two options for format.  Select the VB option, and you should be able to include VBA code.

Actually the macro was developed by someone else and developed using python.  A portion (27 lines) of the 86 lines of python generated code is below:
When calling the stored macro is works until a point and then it stops and throw the error mentioned earlier.  I read a previous post ["PCOMM Not Working In VBA All The Time" from spinningtop on 2009-11-23]  which referenced to same error, and you suggested an emulator patch upgrade which solved the problem with the user.  I did check with IT and below is the emulator version we currently running.  PerhapsIT did not include the specific service patch to address my problem.  
Hopefully this provides better, additional insite into my issue and you additional advice could progress towards a solution.

Thanks

Thats not Python.  That looks like a .MAC format recorded macro file.

Ahh... Should this be converted to .vbs to be compatible with the VBA code which is calling the macro?
Please advise... Thanks

Do you know an easy way to convert a group of AS400 Macros (*.mac) recorded in the PC5250 macro menu within iSeries Access for Windows emulator  to *.vbs using the PCOMM functions, such as "PCOMM.autECLConnList", "PCOMM.autECLSession", etc.)

Any help would be appreciated.

Thanks

Re-record macro.  No conversion mechanism I know of and I've done a lot of IBM I Access for Windows macro automation over the years.

Good news is .MAC format is easily human readable. 

I was hoping I did not need to re-record.  I asked this question in the context of the problem I am having trying to launch a recorded AS400 Macro from a VBA script using the IBM PCOMM functions.  When calling the recorded .mac macro, the macro launches, but runs very fast (seeming to ignore all the "wait" functions, and then it aborts (stops) and pops and error message (below) about 3/4 of the way through the macro.


My thinking is the .mac macro behaves differently when launched from a VBA call versus being manually launched from the IBM I Access for Windows "play/record" menu.  Do you agree with my thinking?  If so, will re-recording the .mac macro as a .vbs script solve my problem.  

Thanks for the guidance.

Can't say I've ever tried to launch a .MAC macro file from a VBA script before, so I can't offer much guidance, there.  I have launched them from BAT scripts and probably Powershell.  I've also called ehllapi directly from VBScript.  

Unfortunately, error 9 isn't very helpful "A system error occurred".

Look at this thread for some general troubleshooting clues.  
https://www.experts-exchange.com/questions/24956712/AS400-PCOMM-Read-Write-Issue-in-VBA.html

Re-recording the macro as a .VBS may or may not help.  Suggest you create a simple test macro and try it.

How exactly are you attempting to launch the MAC macro from Excel VBA?  Can you show me the code?