Enter your search terms Submit search form
	Web pdp-10.trailing-edge.com

TOPS20 Change Order Number 4.2307

Written by: R.ACE		22-Jun-79 07:14:45

Edit checked: NO			   Document: NO
  TCO Tested: NO		Maintenance Release: NO
Hardware-related: NO

Program: MACSYM

Related TCO's:
Related SPR's: 


Problem: THE FLDDB. MACRO USES THE INTRINSIC INSTRUCTION "Z", WHICH
CAN HAVE SOME UNEXPECTED RESULTS IF THE PROGRAMMER DEFINES A SYMBOL
"Z" BEFORE INVOKING THE MACRO.

Diagnosis: NUANCES OF MACRO-20 AND USE OF "Z" IN DEFINITION OF FLDDB.

Solution: IN DEFINITION OF FLDDB., CHANGE <Z LST> TO <0,,LST>

TOPS20 Change Order Number 4.2453

Written by: R.ACE		11-Sep-79 07:14:10

Edit checked: YES			   Document: NO
  TCO Tested: YES		Maintenance Release: NO
Hardware-related: NO

Program: MACSYM

Related TCO's:
Related SPR's: 


Problem: WHEN MACSYM REPORTS AN UNDEFINED SYMBOL, IT SAYS,

	SYMBOL IS NOT DEFINED

THIS DOESN'T CAUSE BATCH JOBS TO BOMB OUT.

Diagnosis: A QUESTION MARK SHOULD PRECEDE THE MESSAGE.

Solution: PUT A QUESTION MARK BEFORE THE MESSAGE, SO IT WILL READ,

	?SYMBOL IS NOT DEFINED

TOPS20 Change Order Number 4.2506

Written by: OSMAN		 2-Oct-79 15:05:14

Edit checked: NO			   Document: NO
  TCO Tested: NO		Maintenance Release: NO
Hardware-related: NO

Program: MACSYM

Related TCO's:
Related SPR's: 


Problem: BRKCH. ","
as a MACRO program line fails.

Diagnosis: MACRO treats comma as an argument separator

Solution: When calling BRK1 in BRKCH., use a dummy variable (%%FOO) which is
set to value of argument, instead of trying to pass argument as a literal
string.

TOPS20 Change Order Number 4.2536

Written by: ZIMA		19-Oct-79 13:32:12

Edit checked: NO			   Document: NO
  TCO Tested: NO		Maintenance Release: NO
Hardware-related: NO

Program: MACSYM

Related TCO's:
Related SPR's: 


Problem: 
     Any use of the MACSYM macro PERSTR generates "U" errors from MACRO.

Diagnosis: 
     The symbol JSMSG0 should be made external.

Solution: 
     Put JSMSG0 in the EXTERN for JSERR0, etc.

TOPS20 Change Order Number 4.2570

Written by: OSMAN		 9-Nov-79 13:44:25

Edit checked: NO			   Document: YES
  TCO Tested: NO		Maintenance Release: NO
Hardware-related: NO

Program: MACSYM

Related TCO's:
Related SPR's: 


Problem: SYMBOL V1 IS USED IN MACSYM AND PROGRAMS THAT SEARCH MACSYM

Diagnosis: IF programs reference V1 before they define V1, they will get
the MACSYM one.

Solution: Change V1 to ..V1, which conforms more to the standard for what
symbols we're allowed to use in monitor universals.