RSTS/E Protection Violation…Final

After the earlier success I decided there is no reason why I need to set the privileged bit to 192 because I’m running from 1,2 so I reran it after a compile without setting the privileged bit to 192. And…it worked. Like you would expect it to. Setting the privileged bit to 192 would allow a non privileged account to run it by running $TAPE05.

So evidently RSTS/E was messing with me the last few days. When I said “I don’t know what to do” 2 days ago, it was because nothing was wrong.

Simulation stopped, PC: 041410 (SOB R1,41406)
sim> att tu0 -r -f aws CUST-TAPE-1000.aws
%SIM-INFO: TU0: unit is read only
%SIM-INFO: TU0: Tape Image 'CUST-TAPE-1000.aws' scanned as AWS format
sim> c

OLD TAPE05

Ready

COMPILE

Ready

DIR TAPE05.*
 Name .Ext    Size   Prot    Date       SY:[1,2]
TAPE05.BAS       6   < 60> 01-Jan-99
TAPE05.BAC      15C  <124> 01-Jan-99

Total of 21 blocks in 2 files in SY:[1,2]


Ready

ASSIGN MM0:

Ready

LIST
NONAME  12:03 AM        01-Jan-99

Ready

RUN TAPE05
 430           11 
 1020          11 

Ready

DIR CUSTRC.*
 Name .Ext    Size   Prot    Date       SY:[1,2]
CUSTRC.TXT     143   < 60> 01-Jan-99

Total of 143 blocks in 1 file in SY:[1,2]


Ready