Problem with results -trying to OPEN/READ and then WRITE output file

[Antoniov.]

Cathy,
I understand only a little of your problem so I can only hint about some tips.
You can add any control code in form of
$ FF[0,8]=12
and write it as
$ WRITE FF
Notice is simplest write only FF without other field but this means you write FF followed by CR+LF (end of line)
Loot at this example:
$! Create a FDL file with my characteristic
$ ANALYZE/RMS/FDL /OUT=TMP.FDL
$! Now I create a empty file
$ CREATE /FDL=TMP.FDL
$! Now open files (look for output file!)
$ OPEN/READ SRC
$ OPEN/APPEND TGT
$! Set up Form Feed code
$ FF[0,8]=12
$! Read loop
$MLOOP:
$ READ SRC SRCLINE/END=EXIT_LOOP
$! Now evaluate SRCLINE in TGTLINE
...
$ IF (eop_condition)
$ THEN
$! write FF followed by new line to avoid
$! CR+LF; TGTLINE cannot exceed 254 bytes
$! see /SYMB differences
$ WRITE TGT FF,TGTLINE
$ ELSE
$ WRITE TGTLINE
$ ENDIF
$ GOTO MLOOP
$EXITLOOP:
$! close with last FF
$ WRITE TGT FF
... etc.

H.T.H.
Antoniov

[Ian Miller.]

To insert the form feed
$ FF[0,8] = 12 ! define symbol for form feed
then use it
$ WRITE SYS$OUTPUT "''FF'Page 1"

[Hein van den Heuvel]

> Jan 16, 2004 15:18:11 GMT N/A: Question Author
>--
> Me again... I still have not had much success.
> I tried to add "carriage_control print" to the record section of the FDL and received an incompatibility message.
> Maybe that type of carriage control is permitted with the other qualifiers????

Well Cathy, that's just not accceptable. :-)

You can do better. It can and will work, so there is a small remaining misunderstanding that needs to be resolved.
I'm convinced that you can figure this out in less time then it takes all of us to second guess you.
Just print a couple of those FDL files and let the data sink in. It's not all that hard, and well documented.

If you do need further help PLEASE help us to help you by providing accurate, exact error message, and critical portions of the commands and/or command files that you know play a role.
So please, attach and input and edited FDL so we can see where the error was made instead of guessing!
(attach is needed instead of text include because this forum stuff makes such a mess of spacing that it makes it unreadable otherwise)

Hein.