From 03e26899e4141277bc20583de6d6673adc291aa1 Mon Sep 17 00:00:00 2001 From: SJLennon Date: Thu, 13 Jul 2023 14:31:56 -0400 Subject: [PATCH] Update Readme.MD --- PGM_REFS/Readme.MD | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/PGM_REFS/Readme.MD b/PGM_REFS/Readme.MD index ef4b1a2..de53020 100644 --- a/PGM_REFS/Readme.MD +++ b/PGM_REFS/Readme.MD @@ -45,7 +45,8 @@ Since many objects will have a library of `*LIBL`, that is what will get passed ### DSPPGMREF Failure -If DSPPGMREF failsinternally, `*ERROR` will appear in the three `USES_*` fields in the REFS file. If you get a lot of these check you have your library list correct. +If DSPPGMREF fails internally, `*ERROR` will appear in the three `USES_*` fields in the REFS file. If you get a lot of these check you have your library list correct. + ## Sample Output File Contents ![Sample ](Images/Sample1.png) @@ -55,4 +56,4 @@ If DSPPGMREF failsinternally, `*ERROR` will appear in the three `USES_*` fields I had difficulty debugging this. 1. I was working on PUB400.COM and the System Debugger in iACS shows the source, but it would never stop on breakpoints. You can debug on the green screen but it isn't as convenient. -2. The DSPPGMREF outfiles are in QTEMP. You can make a single change to put them in one of you libraries if you want to look at them. You will also have to comment out the delete at the bottom of the loop. \ No newline at end of file +2. The DSPPGMREF outfiles are in QTEMP. You can make a single change to put them in one of you libraries if you want to look at them. You will also have to comment out the delete at the bottom of the loop.