To follow up with the outcome:
- We shared our build JCL (BPXBATCH) and script with IBM.
- IBM pointed out a mistake: Our Go build environment setup was in .bashrc,
but "when you run it with BPXBATCH, you don't get a login shell. .profile .bashrc etc will not be run."
- IBM supplied batch JCL that works.
- After this, "The build on z/OS completes OK. The final bind step is memory intensive. The use of a large cache was I think the get out of jail card. Still high CPU for a long time. The result is executable code."
"One batch job using the IBM method but I am sure adding the cache was the principle improvement. Needed large region for the final part."
Thank you,
Mike Baldwin
Cartagena Software Limited
Markham, Ontario, Canada
------------------------------
Mike Baldwin
President
Cartagena Software Limited
Markham ON
1-905-887-0755
------------------------------
Original Message:
Sent: Thu May 26, 2022 12:01 PM
From: Bill O'Farrell
Subject: Go install on z/OS - performance
Hi Mike. I'm the development team lead for Go on z/OS. We are working to reduce memory and compute time for builds. Can you provide more detailed information on what package(s). you are trying to port? With this information we might be able to give you more targeted advice. Thanks
...Bill
------------------------------
Bill O'Farrell
Original Message:
Sent: Thu May 26, 2022 07:07 AM
From: Mike Baldwin
Subject: Go install on z/OS - performance
Hi,
This question is from our team.
Attempting to port a significant go package to z/OS. Following the IBM SDK user guide this process has been one of:
The go install step seems to consume a lot of CPU and memory (had to add additional PAGE datasets).
Are there other approaches that are less CPU/memory intensive?
Thanks,
Mike Baldwin
Cartagena Software Limited
Canada
------------------------------
Mike Baldwin
President
Cartagena Software Limited
Markham ON
1-905-887-0755
------------------------------