Re: Error while listing a saveset file.

From: jay (qwerty_at_asdf.lkj)
Date: 08/31/04 

Date: Tue, 31 Aug 2004 18:08:00 +0530

I tried with the procedure that you mentioned but I get the following
warning message.

syelwatk@oakvms> @reset_backup_saveset_file_attributes.com pvp04501.c

%RMS-W-RTB, 1106 byte record too large for user's buffer

syelwatk@oakvms>

"Z" <z@no.spam> wrote in message news:10j8rj8pppq6693@corp.supernews.com...
> jay wrote:
> > VTXNJ1> set file/att=(rfm:fix,lrl=9216, rat=none) PVP04501_C-NEW.C;1
>
> What makes you think the LRL is 9216?
>
> From another post, by Hoff Hoffman:
>
> This procedure is on Freeware V4.0 and later, in the 000TOOLS area:
>
> --
>
> $! RESET_BACKUP_SAVESET_ATTRIBUTES.COM
> $!
> $! P1 is the specification of the BACKUP saveset
> $!
> $! This procedure resets the record format and record
> $! length attributes of a BACKUP saveset -- savesets
> $! can get "broken" during certain sorts of file
> $! transfers -- such as FTP. This procedure reads the
> $! (undocumented) saveset record attributes directly
> $! out of the target file.
> $!
> $! First render the saveset readable, and implicitly
> $! check that the file exists.
> $!
> $ Set File -
> /Attributes=(RFM:FIX,MRS:512,LRL=512,ORG=SEQ,RAT=NONE) -
> 'p1'
> $
> $ Open/Error=whoops/Read BckSaveset 'p1'
> $ Read/Error=whoops/End=whoops BckSaveset Record
> $ Close/Nolog BckSaveset
> $
> $! Find the blocksize from within the record...
> $
> $ BlockSize = 0
> $ BBH_L_BLOCKSIZE = %x28*8
> $ BlockSize = F$CVUI(BBH_L_BLOCKSIZE, 32, Record)
> $ If BlockSize .lt. 2048 .or. BlockSize .gt. 65535
> $ Then
> $ Write sys$output "Unexpected block size"
> $ Goto whoops
> $ Else
> $ Set File /Attributes=(RFM:FIX,LRL='BlockSize', -
> MRS='BlockSize',RAT=none) -
> 'p1'
> $ endif
> $ exit
> $WHOOPS:
> $ Write sys$output "Error"
> $ exit

Relevant Pages

  • lide: linux ide, just concept idea (Re: coloring stdout && stderr, small kbuild example)
    ... stderr, no cut; stderr out is rare, thus full lines ... buffer; append current line ... $lideSYNTAX ... ' EXIT HUP INT TERM QUIT ...
    (Linux-Kernel)
  • Re: simple read char app return wrong value?
    ... We know that sys_read doesn't return until the user hits "enter" (We would prefer, perhaps, that it did. ... If we need to "flush" some, we read into a different buffer, one at a time, until we find the "enter" key. ... Rather than return the number of bytes read, I've modified the program to return (as an exit code) the character entered. ... mov ecx, the_char; input array ...
    (alt.lang.asm)
  • RE: Buffer Overflow problem
    ... HACK is stored at address 0xbffffa56 ... sh-2.05b# exit ... overflowing the vulnerable buffer, thereby placing ... to facilitate one-on-one interaction with one of our expert instructors. ...
    (Security-Basics)
  • Re: PocketReader mystery
    ... >> for subsequent calls until the buffer is empty ... BASIC reports a 'timeout' error from the SWI at that line, ... immediately on entry into the subroutine. ... ought to behave differently on exit. ...
    (comp.sys.acorn.programmer)
  • Re: Dynamically resizing a buffer
    ... I have a buffer in a program which I write to. ... In this case, the exit() function ... stdout) and then calling exit() is that your user may never see the ... assert macro in conjunction with the exitfunction. ...
    (comp.lang.c)