From: SMTP%"MACRO32@WKUVX1.BITNET" 5-MAY-1993 09:10:13.67 To: EVERHART CC: Subj: re: OPCOM and undocumented logicals X-ListName: "VMS Internals, MACRO, & BLISS Discussions" Warnings-To: <> Errors-To: MacroMan@WKUVX1.BITNET Sender: MacroMan@WKUVX1.BITNET Via: UK.AC.ANGLIA.VA; 5 MAY 93 12:53:06 BST Date: Wed, 5 May 93 12:51 BST From: "Ian Kitching, System Manager" Reply-To: MACRO32@WKUVX1.BITNET To: "macro32%BITNET.WKUVX1"@UK.AC.EARN-RELAY Subject: re: OPCOM and undocumented logicals >From: mcgill >Date: 5 May 93 12:49:44 +1000 >OPCOM includes some sort of reference to (what I am assuming are) >debug options. [...] >*PLEASE* can someone advise what these strings are used for or do, >and if there is anything I can do to use them or otherwise get >OPCOM to dump lots of info. [...] >Craig McGill. >VMS System Programmer. >Canberra. OPCOM debugging works on VMS V5.5-2 - I've just tried it. You need to make a $SNDOPR request to trigger the output. The request uses the "new" (undocumented) format of OPCOM requests that came in with VMS V3.0. [Requests in the documented format are converted on the fly.] The info is written with SHARE priv. to OPC$DEBUG_FILE or otherwise OPC$DEBUG_TERMINAL. The requester needs to have OPER priv. but doesn't need to have an enabled operator terminal. Offset 0 = opc$b_rqstcode: opc$_x_debug = 20 1 = opc$b_scope: opc$k_system = 1 4: debug flags (see below) 26 = opc$t_oprenable_opr: ascic for a valid terminal device (see below) 38 = opc$k_comhdrsiz: end of message Flag bits: The terminal is only there to pass standard 0 full hex info checks on requests - it doesn't need to 1 memory stats be enabled as an operator terminal. 2 operators 3 nodes 4 requests 5 message counters 6 ocd blocks (operators) If anyone is interested in the "new" OPCOM format I can supply the info. Ian Kitching systimk@va.anglia.ac.uk