Re: Combined-Primary (CP) workstn file

Joep,

I think you must have meant S/38, under the S/36 there was RUF (Read Under
Format) which allowed the OCL to put up the screen which would be read by the 
RPG
program.

The S/34 to S/38 migration aid would automatically place a work around to CP 
into
the program.

It amounted to placing a WRITE in the first cycle.  There is no limit to the
number of things one could do within the first cycle.

Read the LDA, fetch a data area, perform a READ loop on a file, call another
program, load a subfile, etc.

Using UC on the data files where the program would WRITE the "what do you want
now" screen, start opening files, then do a READ became a common performance
"enhancement".  More of a smoke & mirrors kind of thing.

Spend time on it? I agree with you, Nahhh

CP workstn files are out of vogue because they depend on the ever efficient,
subtle, cycle.

Just to be a bit cheeky: If one can learn the concepts of OO, inheritance and
polymorphism what the heck makes a cycle so hard to figure out? =;-o

I turn the key and the shaft goes round and round, pistons go up and down, plugs
fire, belts pull, pumps pump, lights glow.  A harmony, nay, orchestra of cycles.
We live with a machine full of cycles every day.  Even if you walk to work: 
left,
right, left, right (except on Mondays when you skip <g>, or Fridays where it's
step, drag, step, drag,<g>)


Joep Beckeringh wrote:

> <snip>

>  On the S/36 there was a
> workaround (basically supplying a string parameter that would be read as the
> first input record), but on the AS/400 it is not very feasible.
>
> (Never tried it with subfiles, though.  Should be possible; shall I try it?
> Nahhh, so many other useless things to try).
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---