Re: VMFPLC2 DUMP malfunction in sixpack 1.2 environment

--- In [email protected], "Dave Wade" <g4ugm@...> wrote:
>
> I think you need to fix you oorexx code. If you look in the original file
> 
> ./ I  01708930 $  1708940 10                          07/13/10 10:06:58
> 
>  INSERTING...    * We update the "VM/370" message on the logo screen as
> well.  .. 01708940
>                           L     R1,FMT77CCW      get address of big logo
> screen HRC370DK   01708950
>                           MVC   8(1,R1),INSTWRD1       zap with 7 or 8 from
> PSA HRC370DK 01708960 
> 
> is the last four lines in the end of the file. You are trying to parse the
> garbage in the end of the last block.
> VMFPLC2 ALWAYS writes a full block. You need to look in the parms block to
> see where the last file ends.
> If you search you will find that the line deleting comment:-
> 
> "LOGOSIZE EQU   FMTLOGO+6"
> 
> occurs 100 lines previous, and as the file is 800-byte fixed blocks on disk
> I make that one block back.
> 
> Dave Wade G4UGM
> Illegitimi Non Carborundum
> 
> P.S. The "C" code in the 
> 
> http://games.groups.yahoo.com/group/H390-VM/files/PC%20Utilities/
> 
> has some code that does this. It also reads the file properley.
> 

Dave,

I reproduced the 'error' using VM/370 Sixpack 1.2 (looking at AWS tape file with an EBCDIC editor), and I obtained the same resuslts.
Then I started VMFPLC2 on VM/SP (accessing the DMKGRF UPDLOG on the VM/370 SixPack minidisk) and i got an AWS file without ending garbage (at the end I found just a few  x'00' and tape marks).
So perhaps the problem lies only in VMFPLC2 of VM/370.

Regards.

Paul