NOTES:
 
	THIS VERSION OF THE INDIRECT COMMAND PROCESSOR IS SETUP FOR RSX-11D V6B
OR IAS V1.1.  THIS IS ESSENTIALLY THE SAME PROGRAM FROM RSX-11M, CONDITIONALLY
ASSEMBLED TO SUPPORT RSX-11D EXECUTIVE DATA STRUCTURES.  ALL OF THE COMMAND
OPTIONS FROM RSX11M V3 ARE SUPPORTED (AT LEAST THOSE INCLUDED IN RSX11M AS OF
9-JUN-76 OR THEREABOUT).  THE ONLY AVAILABLE DOCUMENTATION IS IN THE MODULE
'INDRCT.MAC', WHERE THE SOURCE LISTS THE VARIOUS CONTROL COMMANDS TO THE 'AT.'
PROCESSOR.  FOR ADDITIONAL INFORMATION, OR AN INTRODUCTION TO THE CONCEPTS OF
THE INDIRECT MCR FUNCTION, THE USER SHOULD ATTEMPT TO LOCATE AN RSX-11M MANUAL.
FUNCTIONALLY, THE RSX-11M AND RSX-11D VERSIONS OF THE INDIRECT COMMANDER ARE
IDENTICAL.
 
	AS THE SOURCES ARE INCLUDED IN THIS PACKAGE, THE SYSTEM SPECIFIC COM-
PONENTS CAN BE MODIFIED TO RUN ON ANY RSX-11D SYSTEM (OLDER VERSIONS).  THE
ONLY MODIFICATIONS REQUIRED ARE IN THE ROOT ('INDRCT') WHERE THE COMMAND LINE
IS QUEUED, AND IN THE SPECIAL SUBROUTINES WHICH SEARCH THE SYSTEM LISTS (STD,
ATL, & MRL).
 
	THE USER WILL NOTE THAT A NEW VERSION OF MCR IS ALSO BUILT AS A BY-
PRODUCT OF THE '...AT.' CREATION PROCESS.  MCR HAS BEEN MODIFIED TO CHECK FOR
AN '@' CHARACTER IN THE FIRST POSITION OF AN MCR LINE, AND IF ONE IS FOUND, PASS
THE COMMAND LINE ON TO '...AT.'.  AS MCR REQUIRES THE SYMBOL TABLE FILE FROM
'MCRERR' WHEN IT IS TASKBUILT, IT MIGHT BE ADVISABLE FOR THE USER TO SUBSTITUTE
HIS OWN VERSION OF MCRERR'S .STB FILE, RATHER THAN USE THE ONE SUPPLIED HERE.
TO REPLACE MCR WHILE THE SYSTEM IS RUNNING:
	MCR>INS [300,15]MCR/TASK=MCR
	MCR>RUN MCR 1M
	MCR>REM ...MCR<ESC>
	(WAIT UNTIL MCR PROMPTS 1 MINUTE LATER)
	MCR>INS [300,15]MCR
	MCR>REM MCR
 
	MCR AND '...AT.' WILL RUN WITH NO PROBLEM ON AN IAS SYSTEM.  THE IN-
DIRECT COMMANDER WILL ALWAYS WORK BEFORE TIMESHARING IS BROUGHT UP, AND MAY ALSO
BE ENABLED WHEN TIMESHARING IS RUNNING.  TO ENABLE MCR WHEN TIMESHARING IS UP,
THE TERMINALS WHICH WILL USE MCR MUST NOT BE TIMESHARING TERMINALS (IE THE
IAS 'SET TERMINALS' STARTUP COMMAND MUST NOT INCLUDE THESE TERMINALS).  TWO
ADDITIONAL STEPS ARE THEN REQUIRED.  USE 'SYS /DEV' TO GET THE PUD ADDRESSES OF
THESE TERMINALS (UNDER MCR INTERFACE) AND 'OPE' TO OPEN THE SECOND WORD IN EACH
PUD.  'OR' IN 4000(8) WITH THE EXISTING VALUE. E.G.
	MCR>SYS /DEV
	.
	.
	TT5 143000 **
	.
	.
	MCR>OPE 143002/KNL
	143002/100005 104005<ESC>
FINALLY, BRING UP TIMESHARING AND UNDER SCI (OR PDS) ENABLE ...MCR AS FOLLOWS:
	PDS>ENABLE/REALTIME ...MCR
THE REALTIME TERMINALS WILL BE FUNCTIONALLY IDENTICAL TO RSX-11D TERMINALS.  IF
THE USER HAS 'HEL', 'BYE' AND 'PWD', THEN HE CAN SUPPORT LOGGING IN, ETC.  IF
HE DOES NOT HAVE THESE PROGRAMS (DEPENDING UPON WHAT GETS BY ON THE IAS DIS-
TRIBUTION TAPES), ONE ADDITIONAL STEP IS REQUIRED.  OPEN THE TERMINAL PUD AS
SHOWN ABOVE AT PUD ADDRESS + 52.  MAKE THEIS WORD A '5'.  THIS WILL SET THE
TERMINAL AS LOGGED IN AND PRIVILEDGED.
 
	THERE APPEARS TO BE A MINOR BUG IN '...AT.' THAT OCCURS WHEN IT IS
TASKBUILT AS MULTIUSER.  IT WILL HANG UP WAITING FOR THE CURRENT OPERATION TO
FINISH, EVEN THOUGH IT ALREADY IS DONE.  THIS OCCURS BECAUSE THE DISTRIBUTED
VERSION DOES TWO ATL SCANS: THE FIRST TO FIND THE TASK JUST INITIATED, AND THE
SECOND (AND SUBSEQUENT) TO SCAN THE ATL UNTIL IT DISAPPEARS.  BECAUSE THE
'...AT.' TASK RUNS AT SUCH A LOW PRIORITY, IT CAN EASILY LOSE CONTROL TO ANY
TASK IT SPAWNS WHICH BURNS THE CPU.  WHEN IT FINALLY GETS TIME TO RUN (THIS
IS ESPECIALLY THE CASE WITH MULTIPLE COPIES IF IT IS MULTIUSER), IT LOOKS FOR
THE TASK TO APPEAR ON THE ATL.  BUT SINCE IT HAS ALREADY FINISHED, IT NEVER
WILL.  NOTE, ALSO, THAT WITHOUT TIMESLICING ON A 'D' SYSTEM, OR ON ANY IAS
SYSTEM, THE 'NULL TASK' CODE IN '...AT.' WILL ALLOW ONLY THE HIGHEST COPY
ON THE ATL TO RUN.
	THESE PROBLEMS HAVE BEEN CORRECTED BY THE FRUSTRATED LIBRARIAN, AND
THE FIXES ARE AVAILABLE THROUGH THE 'SLIPR' FILES INCLUDED IN THIS ACCOUNT.
I MOST STRONGLY RECOMMEND THESE FIXES BE APPLIED.  ADDITIONALLY, THE FIXES
SUPPORT THE '$$$' IAS TASKNAMES AND ALL OF THE MFT FUNCTIONS.  (WARNING: THE
SLIPR FILES ARE RSX11D V6.2 SLIPR -- THERE IS AN AUDIT TRAIL FEATURE WHICH
WILL PROBABLY NOT WORK WITH EARLIER VERSIONS OF SLIPR.  IT SHOULD BE FAIRLY
SIMPLE TO EDIT THESE FILES INTO THE CORRECT EARLIER SYNTAX IF YOU DO NOT HAVE
RSX11D V6.2 OR RSX11M V3).