Hi João, The problem is likely the scope of the system variable. &SYSECT has LOCAL scope, which restricts its usage somewhat. If you try &SYSDATE or another sys var with GLOBAL scope, that should work.
HTH, Mike -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of João Reginato Sent: Friday, December 30, 2022 10:05 AM To: [email protected] Subject: ASMA003E Undeclared variable symbol SYSECT Caution! This message was sent from outside your organization. Hi Why '&sysect' works fine inside a MACRO call but not in the program body out of a macro?? WTO '&SYSECT start' ** ASMA003E Undeclared variable symbol; default=0, null, or type=U - OPENC/SYSECT Any tips? TIA João Very happy new year for everybody -- O software antivírus Avast realizou uma checagem de vírus neste e-mail. www.avast.com
