Trailing-Edge
-
PDP-10 Archives
-
BB-J992D-SB_1984
-
ibmcom.bwr
There are 3 other files named ibmcom.bwr in the archive. Click here to see a list.
Beware file for IBMCOM
COPYRIGHT (C) DIGITAL EQUIPMENT CORPORATION 1983,1984
THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED
AND COPIED ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE
AND WITH THE INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS
SOFTWARE OR ANY OTHER COPIES THEREOF MAY NOT BE PROVIDED OR
OTHERWISE MADE AVAILABLE TO ANY OTHER PERSON. NO TITLE TO
AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED.
THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE
WITHOUT NOTICE AND SHOULD NOT BE CONSTRUED AS A COMMITMENT
BY DIGITAL EQUIPMENT CORPORATION.
DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY
OF ITS SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY
DIGITAL.
1. The IBMCOM tape you receive has three savesets on it:
Documentation files, Binary files and Source Files. Please
restore all files from all three savesets.
2. Please note: the two monitor modules are included on
the monitor tape. They are D60SER and D6SINT. If you
are installing IBMCOM for the first time, then it will be
necessary for you to follow the monitor rebuilding
instructions in the TOPS-10 IBM Emulation/Termination manual,
AA-D612B-TB. It will not be necessary for you to rebuild
your current monitor if this tape is sent you as an update,
and your current configuration supports IBMCOM.
3. The TOPS-10 IBM Emulation/Termination manual contains
information on using the IBM communications software with the
DL10. Ignore this information (the DL10 is no longer
supported on TOPS-10) which will be removed in a possible
later version of the manual. This comment also applies to
the information on BOOT11, the loader for the DL10.
4. If no network software (ANF10) is installed in the monitor,
QUASAR will have some difficulties dealing with its node data
base. To solve this problem, either install ANF10 in the
monitor or add the following patches to QUASAR.
File 1) DSKB:QSRADM.ORI created: 0956 22-Feb-83
File 2) DSKB:QSRADM.MAC created: 1303 25-Feb-83
1)29 PJRST SNDOPR ;RETURN THE MSG TO ORION AND RETURN
****
; Insert one line at DN60.1 plus one line
2)29 MOVEI S1,G$MSG ;Get the object block address
2) ; for coverage... It is not actually
2) ; used ultimatly but is needed to
2) ; prevent ILM.
2) PJRST SNDOPR ;RETURN THE MSG TO ORION AND RETURN
**************
1)48 MOVEM S1,OBJ.ND(P1) ;SYSTEM'IZE IT (NBR ON -10)
1) MOVE P2,S2 ;SAVE THE NODE DATA BASE ENTRY ADDRESS
****
; Comment out a line at GETOBJ+4
2)48 ; MOVEM S1,OBJ.ND(P1) ;SYSTEM'IZE IT (NBR ON -10)
2) MOVE P2,S2 ;SAVE THE NODE DATA BASE ENTRY ADDRESS
**************
Page 1
File 1) DSKB:QSRDSP.ORI created: 0955 22-Feb-83
File 2) DSKB:QSRDSP.MAC created: 0957 22-Feb-83
**************
1)3 BYTPTR: BLOCK 1 ;BYTE POINTER FOR $TEXT ROUTINE.
****
2)3 KLUDGE: BLOCK 1 ;Kludge flag to handle sho q conflicts
2) BYTPTR: BLOCK 1 ;BYTE POINTER FOR $TEXT ROUTINE.
**************
1)9 SKIPN S2,OBJ.ND(S2) ;IF NO NODES,
1) JRST CHKO.1 ;WIN,,CHECK FOR DN60 EMULATION
1) CAME S2,[-1] ;IF ALL NODES,
1) CAMN S2,NETNAM(P1) ; OR IF WE MATCH BY NAME,
1) SKIPA ;THEN CHECK FOR DN60 EMULATION
1) CAMN S2,NETNBR(P1) ;IF WE MATCH BY NODE NUMBER,
1) SKIPA ;THEN CHECK FOR DN60 EMULATION
1) $RETF ;ELSE RETURN FALSE
1) CHKO.1: MOVE S1,OBJSCH(T1) ;GET THE SCHEDULING BITS
****
; Change some lines beginning at CHKO.0: plus 6 lines.
2)9 MOVE S2,OBJ.ND(S2) ;Get this object node
2) CAMN S2,[-1] ;Is it all nodes?
2) JRST CHKO.1 ;Yes, skip this
2) MOVE S1,OBJNOD(T1) ;Get the object's node
2) $CALL N$MTCH ;Check for match
2) $RETIF ;Quit if not this one
2) CHKO.1: MOVE S1,OBJSCH(T1) ;GET THE SCHEDULING BITS
**************
1)15 MOVE S1,NETCOL(P1) ;GET THIS NODES NAME/NUMBER
1) PUSHJ P,CMPNOD ;IS IT ONE WE WANT ???
1) JUMPF NPRM.3 ;NO,,TRY NEXT
1) MOVE S1,NETCOL(P1) ;GET THE NODE NAME/NUMBER
1) PUSHJ P,N$NODE## ;FIND THAT NODE IN OUR DATA BASE
****
; Add a line at NPRM.1 plus 1 line
2)15 SKIPN S1,NETCOL(P1) ;Get node number, is it 0?
2) MOVE S1,NETLOC(P1) ;Yes, get node name
2) PUSHJ P,CMPNOD ;IS IT ONE WE WANT ???
2) JUMPF NPRM.3 ;NO,,TRY NEXT
; Add a line at NPRM.1 plus 4 lines
2) SKIPN S1,NETCOL(P1) ;Get node number, is it 0?
2) MOVE S1,NETLOC(P1) ;Yes, get node name
2) PUSHJ P,N$NODE## ;FIND THAT NODE IN OUR DATA BASE
**************
Page 2
File 1) DSKB:QSRDSP.ORI created: 0955 22-Feb-83
File 2) DSKB:QSRDSP.MAC created: 0957 22-Feb-83
**************
1)41 DEPOUT: SKIPN NODE6B ;CHECK FOR KLUDGE
1) SKIPA S1,[-1] ;MAKE IT WILD
****
2)41 DEPOUT: SKIPN KLUDGE ;Check for kludge
2) SKIPA S1,[-1] ;MAKE IT WILD
**************
1)41 JUMPF .POPJ ;RETURN IF FALSE OR NO MATCH
****
; Add one line at DEPBAT plus 3 lines.
2)41 SKIPE KLUDGE ;Check for kludge
2) JUMPF .POPJ ;RETURN IF FALSE OR NO MATCH
**************
1)55 GETP.2: MOVE T1,NODE6B ;GET /NODE
1) CAMN T1,[-1] ;WAS /NODE SPECIFIED?
****
2)55 GETP.2: SETOM KLUDGE ;Say no kludge
2) MOVE T1,NODE6B ;GET /NODE
2) CAMN T1,[-1] ;WAS /NODE SPECIFIED?
**************
1)55 SETZM NODE6B ;FLAG KLUDGE
1) $RETT ;AND RETURN
****
; Change one line at GETP.2 plus 10 lines
2)55 SETZM KLUDGE ;FLAG KLUDGE
2) $RETT ;AND RETURN
**************
Page 3
File 1) DSKB:QSRNET.ORI[50,5614] created: 0957 22-Feb-83
File 2) DSKB:QSRNET.MAC[50,5614] created: 1031 22-Feb-83
1)9 N$GNOD: $SAVE <P1> ;SAVE P1 FOR A MINUTE
1) SETZ P1, ;Clear P1
****
2)9 N$GNOD: $SAVE <S1,P1> ;SAVE S1 and P1 FOR A MINUTE
2) $CALL CONOD ;Check the node identifier
2) SETZ P1, ;Clear P1
**************
1)23 CAME S1,NETNAM(S2) ;S2 POINTS TO FIRST NAME'S DB ENTRY
****
; Add one line at N$MTCH plus 5 lines
2)23 $CALL CONOD ;Check the node identifier
2) CAME S1,NETNAM(S2) ;S2 POINTS TO FIRST NAME'S DB ENTRY
**************
1)28 CAME S1,NETNAM(S2) ;DO
****
; Add one line at FNDD.0 plus 3 lines
2)28 $CALL CONOD ;Check the node number
2) CAME S1,NETNAM(S2) ;DO
**************
1)35 END
****
; Add a new routine at the end of the module.
2)35 SUBTTL CONOD Compare node to 0
2) ; Called with S1 containing a node identifier. If 0, then set to
2) ; the local node name if the local node number is 0.
2) CONOD: SKIPE S1 ;Is node number 0?
2) JRST CONO.1 ;No
2) SKIPN G$LNBR ;Local node 0?
2) MOVE S1,G$LNAM ;Use local node name
2) CONO.1: $RET
2) END
**************
5. Since the first release of V4.0 of TOPS-10 2780/3780 E/T and
V1.0 of TOPS-10 2780/3780/HASP, several problems have been
reported. The following SPRs describe the problems and their
solutions.
SPR: 10-34280
[Symptom]
IBMSPL gets ILMs when FTFACT is non-zero.
[Diagnosis]
In routine DOFACT the LOAD macro is used incorrectly to load the
queue name, the sequence number and the number of records
processed. Since the DATAST, $ and $. macros produce symbols
which contain an implicit index register, references to these
symbols with the LOAD and STORE macros must leave their position
fields blank.
[Cure]
Change the code in DOFACT to use the LOAD macro to properly
reference T.QNM,T.SEQ and T.NRS.
[FILCOM]
File 1) DSK:IBMSPL.XXX[4,177] created: 1411 21-Feb-1983
File 2) DSK:IBMSPL.MAC[4,177] created: 1007 17-Nov-1983
1)4 &
****
2)4 4(354) 11-Nov-83 GKN SPR 10-34280 Fix possible ILMs with incorrect
2) LOAD S1,T.QNM (should be LOAD S1,,T.QNM).
2) &
**************
1)130 LOAD S1,T.QNM ;Get the queue name
1) TLZ S2,77 ;CLEAR JUNK
1) IOR S1,S2 ;INSERT QUEUE NAME
1) IORM S1,FACTBL+3 ;NODE NUMBER ALREADY STORED FROM ABOVE
1) SETZM FACTBL+4 ;no runtime
1) SETZM FACTBL+5 ;no core time intergral
1) SETZM FACTBL+6 ;no disk reads
1) SETZM FACTBL+7 ;no disk writes
1) MOVE S1,[SIXBIT /IBM /] ;Make up a device name
1) MOVEM S1,FACTBL+10 ;store it
1) LOAD S1,T.SEQ ;Sequence number
1) MOVEM S1,FACTBL+11 ;STORE
1) LOAD S1,T.NRS ;Number of units processed
1) MOVEM S1,FACTBL+12 ;STORE
****
2)130 LOAD S1,,T.QNM ;[354] Get the queue name
2) TLZ S2,77 ;CLEAR JUNK
2) IOR S1,S2 ;INSERT QUEUE NAME
2) IORM S1,FACTBL+3 ;NODE NUMBER ALREADY STORED FROM ABOVE
2) SETZM FACTBL+4 ;no runtime
2) SETZM FACTBL+5 ;no core time intergral
2) SETZM FACTBL+6 ;no disk reads
2) SETZM FACTBL+7 ;no disk writes
2) MOVE S1,[SIXBIT /IBM /] ;Make up a device name
2) MOVEM S1,FACTBL+10 ;store it
2) LOAD S1,,T.SEQ ;[354] Sequence number
2) MOVEM S1,FACTBL+11 ;STORE
2) LOAD S1,,T.NRS ;[354] Number of units processed
2) MOVEM S1,FACTBL+12 ;STORE
**************
SPR: 10-34395
[Symptom]
?Illegal address in UUO at user PC xxxxxx
[Diagnosis]
The UUO which is causing the problem is the QUEUE. UUO at
WRTUSG:. IBMSPL uses the USTXT. macro to create an entry in the
argument block for the QUEUE. UUO incorrectly. There are three
occurances of:
USTXT. (<-1,,[ASCIZ / /]>) ;SYSTEM TEXT
in the code. The macro expands to two words which look something
like:
XWD 10,112
Z @string_address(17)
The indirect bit and the index AC (17, in this case) appear
because the argument is masked with 37777777 when the macro is
expanded. This is clearly an incorrect address. An interesting
aside is that under certain circumstances this address, though
incorrect, may indeed be legal in the sense that it is within the
confines of IBMSPL's virtual address space.
[Cure]
Correct the usage of the USTXT. macro in IBMSPL. This will fix
IBMSPL such that it no longer generates incorrect addresses.
[FILCOM]
File 1) DSK:IBMSPL.OLD[4,177] created: 1007 17-Nov-1983
File 2) DSK:IBMSPL.MAC[4,177] created: 1330 16-Dec-1983
1)3 XP IBMEDT, 351 ; Edit level
1) XP IBMWHO, 0 ; Who did last edit (0=DEC)
****
2)3 XP IBMEDT, 355 ; Edit level
2) XP IBMWHO, 0 ; Who did last edit (0=DEC)
**************
1)4 &
****
2)4 4(355) 16-Dec-83 GKN Fix part of the problem with ?Illegal address
2) in UUO executing QUEUE. UUOs. IBMSPL feeds
2) the monitor a bogus string pointer in the
2) system text field.
2) &
**************
1)131 USTXT. (<-1,,[ASCIZ / /]>) ;SYSTEM TEXT
1) USICN. (0,US%IMM) ;CONNECT TIME
****
2)131 USTXT. (<[ASCIZ / /]>) ;[355] System text
2) USICN. (0,US%IMM) ;CONNECT TIME
**************
1)131 USTXT. (<-1,,[ASCIZ / /]>) ;SYSTEM TEXT
1) USNM2. (<POINT 7,.EQOWN(J)>) ;USER NAME (TOPS20)
****
2)131 USTXT. (<[ASCIZ / /]>) ;[355] System text
2) USNM2. (<POINT 7,.EQOWN(J)>) ;USER NAME (TOPS20)
**************
1)132 USTXT. (<-1,,[ASCIZ / /]>) ;SYSTEM TEXT
1) TOPS10< ;TOPS-10 ONLY
****
2)132 USTXT. (<[ASCIZ / /]>) ;[355] System text
2) TOPS10< ;TOPS-10 ONLY
**************
SPR: 10-34413
[Symptom]
Spurious CRLF sequences appear in output returning from
an IBM host.
[Diagnosis]
Additional end of line processing with edit 33 installed
in XL3780.P11 may introduce an extra CRLF in some situations.
[Cure]
Remove edit 33 from module XL3780.P11 of the Tops-10 version 4
2780/3780 ET product.
[FILCOM]
File 1) DSK:XL3780.P11[4,206] created: 1530 30-Oct-1982
File 2) DSK:XL3780.FIX[4,206] created: 1915 03-Jan-1984
1)2 V3780=033
1) VEDIT=VEDIT+V3780
****
2)2 ; 4(034) 2-JAN-84
2) ; remove edit 33
2) V3780=034
2) VEDIT=VEDIT+V3780
**************
1)24 BEQ 40$ ;no, done with this chunk
1) DEC R3 ;yes, count down counter
****
2)24 BEQ 22$ ;no, done with this chunk
2) DEC R3 ;yes, count down counter
**************
1)24 41$: CALL XLIPRS ;yes, process an irs
1) BR 14$ ;process next character
****
2)24 CALL XLIPRS ;yes, process an irs
2) BR 14$ ;process next character
**************
1)24 ;end of message - check if we need to do end of line processing
1) 40$: TST TCHPS(R5) ;if at beginning of line...
1) BEQ 22$ ;then we don't have to worry
1) BIT #TCPRI,TCFG1(R5) ;lpt?
1) BNE 41$ ;yes - go do lpt IRS
1) BR 31$ ;no - do cdr IRS
1) ; card mode -- check for irs
****
2)24 ; card mode -- check for irs
**************
[End of IBMCOM beware file]