What if there is a SYSTERM but no SYSPRINT?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf of Jonathan Scott [jonathan_sc...@vnet.ibm.com] Sent: Wednesday, November 30, 2022 9:14 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Battling CDAHLASM obfuscations and an ASMA90 RC=16 termination I don't have any further debugging suggestions except to try to contact CDAHLASM people (presumably the C compiler area) to see if they have any ideas. There's no fixed rule about when a given HLASM message appears on the job log rather than SYSPRINT. What actually happens is that if it needs to write out a message but it can't print it (because the listing file is not open or cannot be used) it tries to write it with WTO ROUTCDE=11. This means that certain messages will always get written to the job log (for example being unable to open SYSPRINT when needed) but others depend on the sequence of events. Jonathan Scott, HLASM IBM Hursley, UK
