Nah, I don't blame my tools or the steak -- I blame you!
You're the cause of all my woes :-)
Think that problem was a bad one, wait for this one --
CALL INTRINSIC "GETPRIVMODE"
CALL INTRINSIC "FWRITE" USING WS-FETIPAS2-FNUM
WS-FETIPAS2-RECORD
WS-FIELD-LENGTH
\0\
The file is a PRIV mode, KSAMXL lockworded file that was previously FOPENed
and returned a file number = +0021
So, the FWRITE fails with an error code = 45 (PRIVILEGED FILE VIOLATION)
Huh? I've no idea how that can happen.
I am not expecting any constructive answers to this one so I am just
documenting this for posterity.
I'm sure I'll figure it out eventually.
On Sun, 13 Jul 2008 22:49:37 -0500, Denys Beauchemin <[log in to unmask]> wrote:
>Shawn, great answer.
>
>Another one is something about someone blaming his tools for his errors.
>
>Denys
>
>-----Original Message-----
>From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
>Of Shawn Gordon
>Sent: Sunday, July 13, 2008 4:13 PM
>To: [log in to unmask]
>Subject: Re: [HP3000-L] Cannot Purge PRIV mode File Problem
>
>At 02:09 PM 7/13/2008, Brian Donaldson wrote:
>>One thing I did forget to mention was that once I have the eight char
>>(lowercase or uppercase) lockword, I am using the AIF intrinsic AIFFILEGPUT
>>to plug the lockword into the file.
>>
>>So I am assuming that the AIF isn't smart enough to upshift all the
>>letters before plugging the lockword into the file.
>
>that's like blaming the steak for not cooking itself to the right
>temperature.
>
>
>
>>Brian.
>>
>>
>>On Sun, 13 Jul 2008 17:04:05 -0400, Brian Donaldson
>><[log in to unmask]> wrote:
>>
>> >Nope, the lockword was created in a Cobol program running under the MPEiX
>> >directory, not the shell.
>> >
>> >This problem only seems to occur if the lockword has lower-case chars but
>> >I can purge the file via MPEX ok if the lockword is in upper-case.
>> >
>> >So I had to fix my routine that creates the random lockword (password)
>> >to restrict it to upper-case chars (and numbers) only.
>> >
>> >Brian.
>> >
>> >On Sun, 13 Jul 2008 12:04:10 -0700, Bahrs, Art
><[log in to unmask]>
>> >wrote:
>> >
>> >>Hi Brian
>> >> Not an expert here but I don't remember the ability in the lockword
>> >handlers to support lower case chars
>> >>
>> >> Could the lockword have been established in the shell? Might have
>been
>> >established programtically ther?
>> >>
>> >>
>> >>Sent via PDA
>> >>Thanks
>> >>Art Bahrs
>> >>Security Engineer
>> >>[log in to unmask]
>> >>
>> >>-----Original Message-----
>> >>From: Brian Donaldson <[log in to unmask]>
>> >>Sent: Sunday, 13 July, 2008 9:58 AM
>> >>To: [log in to unmask] <[log in to unmask]>
>> >>Subject: Re: Cannot Purge PRIV mode File Problem
>> >>
>> >>I was able to whack the file (finally) via a nasty little program named
>> >>FSCHECK.MPEXL.TELESUP
>> >>
>> >>However, this still leaves me wondering why I couldn't purge the file
>> >>because it had lowercase chars in the lockword.
>> >>
>> >>Anyone know why?
>> >>
>> >>Brian.
>> >>
>> >>On Sun, 13 Jul 2008 12:37:08 -0400, Brian Donaldson <[log in to unmask]>
>>wrote:
>> >>
>> >>>FILE: xxxxx.PUB.SYS
>> >>>
>> >>>FILE CODE : -201 FOPTIONS: ASCII,FIXED,NOCCTL,STD
>> >>>BLK FACTOR: 8 CREATOR : MANAGER.SYS
>> >>>REC SIZE: 32(BYTES) LOCKWORD: hMOGhF2m
>> >>>BLK SIZE: 256(BYTES) SECURITY--READ : ANY
>> >>>EXT SIZE: 0(SECT) WRITE : ANY
>> >>>NUM REC: 0 APPEND : ANY
>> >>>NUM SEC: 0 LOCK : ANY
>> >>>NUM EXT: 0 EXECUTE : ANY
>> >>>MAX REC: 1024 **SECURITY IS ON
>> >>> FLAGS : NO ACCESSORS
>> >>>NUM LABELS: 0 CREATED : SUN, JUL 13, 2008, 9:14 AM
>> >>>MAX LABELS: 254 MODIFIED: SUN, JUL 13, 2008, 9:14 AM
>> >>>DISC DEV #: 2 ACCESSED: SUN, JUL 13, 2008, 9:14 AM
>> >>>SEC OFFSET: 65024 LABEL ADDR: $0000005E.$002C6420
>> >>>VOLCLASS : MPEXL_SYSTEM_VOLUME_SET:DISC
>> >>>
>> >>>
>> >>>:MPEX
>> >>>
>> >>>MPEX/3000 29N00420 (c) VESOFT Inc, 1980 6.5 03:04918 For help type
>>'HELP'
>> >>>
>> >>>Hint: %PRINT @.DOC;SEARCH="CUST_NUM";PREV="PROCEDURE" or "FUNCTION";NUM
>> >>> shows you all lines containing CUST_NUM and the
>> immediately preceding
>> >>> lines that contain PROCEDURE or FUNCTION (i.e. the
>> procedure headers).
>> >>>
>> >>>%ALTFILE LOCKERD2;CODE=0
>> >>>-----Altering LOCKERD2.PUB.SYS
>> >>>LOCKWORD VIOLATION (FSERR 92)
>> >>>Error: Doing Fopen of LOCKERD2/.PUB.SYS.
>> >>>%PURGE LOCKERD2
>> >>>-----Will purge LOCKERD2.PUB.SYS (code "PRIV", type FA, EOF 0, 0
>sectors)
>> >>>OK to purge 1 file (y/N)? Y
>> >>>-----Purging LOCKERD2.PUB.SYS (0 sectors)
>> >>>LOCKWORD VIOLATION (FSERR 92)
>> >>>Unable to purge file "LOCKERD2/.PUB.SYS". (CIERR 384)
>> >>>%REDO
>> >>>
>> >>>PURGE LOCKERD2/hMOGhF2m
>> >>>
>> >>>-----Will purge LOCKERD2.PUB.SYS (code "PRIV", type FA, EOF 0, 0
>sectors)
>> >>>OK to purge 1 file (y/N)? Y
>> >>>-----Purging LOCKERD2.PUB.SYS (0 sectors)
>> >>>LOCKWORD VIOLATION (FSERR 92)
>> >>>Unable to purge file "LOCKERD2/.PUB.SYS". (CIERR 384)
>> >>>%
>> >>>EXIT
>> >>>
>> >>>END OF PROGRAM
>> >>>
>> >>>:FILE T;DEV=DISC
>> >>>
>> >>>:FILE T;DEV=DISC
>> >>>:STORE LOCKERD2.PUB.SYS;*T;PURGE
>> >>> >> TURBO-STORE/RESTORE VERSION C.65.19 B5152AA <<
>> >>> (C) 1986 HEWLETT-PACKARD CO.
>> >>>
>> >>>STORE LOCKERD2.PUB.SYS;*T;PURGE
>> >>>
>> >>>SUN, JUL 13, 2008, 9:23 AM
>> >>>
>> >>>
>> >>>FILES STORED : 1
>> >>>
>> >>>
>> >>>TOTAL MEDIA WRITTEN : 1
>> >>>
>> >>>LOCKWORD VIOLATION (FSERR 92)
>> >>>LOCKERD2.PUB .SYS NOT PURGED: LOCKWORD VIOLATION ENCOUNTERED
>ON
>> >>> FILE OPEN
>> >>>
>> >>>
>> >>>How on earth do I get rid of this file? It has a lockword with
>lowercase
>>chars
>> >>>in it and I cannot purge the file.............! (even when I give it
>the
>> >>>correct
>> >>>lockword)
>> >>>
>> >>>TIA,
>> >>>Brian.
>> >>>
>> >>>* To join/leave the list, search archives, change list settings, *
>> >>>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>> >>
>> >>* To join/leave the list, search archives, change list settings, *
>> >>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>> >>
>> >>
>> >>DISCLAIMER:
>> >>This message is intended for the sole use of the addressee, and may
>contain
>> >information that is privileged, confidential and exempt from disclosure
>> >under applicable law. If you are not the addressee you are hereby
>notified
>> >that you may not use, copy, disclose, or distribute to anyone the message
>or
>> >any information contained in the message. If you have received this
>message
>> >in error, please immediately advise the sender by reply email and delete
>> >this message.
>> >>
>> >>* To join/leave the list, search archives, change list settings, *
>> >>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>> >
>> >* To join/leave the list, search archives, change list settings, *
>> >* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>>
>>* To join/leave the list, search archives, change list settings, *
>>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
>Regards,
>
>Shawn Gordon
>President
>theKompany.com
>www.thekompany.com
>www.mindawn.com
>949-713-3276
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>No virus found in this incoming message.
>Checked by AVG - http://www.avg.com
>Version: 8.0.138 / Virus Database: 270.4.10/1550 - Release Date: 7/13/2008
>5:58 PM
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
