Re: 'IBM says it's time to dich PDM/SEU'? -- COBOL400-L

Jim Essinger wrote:

   4. Re:  'IBM says it's time to dich PDM/SEU'? (Jim Essinger)
You are welcome David. Just so you know, if you really can't give upyourblock cut, copy, move etc, commands in the sequence number area, Ibelievethat WDSC LPEX editor supports those commands in the sequence numberarea ofit's editor. I didn't like how I had to get over there to key thecommands,so I learned the alt + L to highlight a line, then a few lines up ordown doit again to highlight a block, and then use alt + (C to copy, M tomove, D
to delete) the highlighted lines. I think once you learn it it is much
faster, and easier to see errors in coding, lines that have beencommented
out (different color) etc.



Jim:

Nice to know, but that doesn't describe what a 'block copy' is to me.

A block-copy doesn't copy a "block" of lines. A block-copy involves aselection of a rectangular area some fixed-number of columns wide and afixed-number of rows deep. For example, I might select colums 15-30 inrows 20-25. I would then copy that rectangular area to columns 10-25 inrows 10-15.

I do this kind of copy regularly for different source types. In CL, Imight have a list of PGM PARM() variables that I want to create DCLsfor. Since I always create the PGM statement so that each PARM() valueis on a separate line, I can block-copy the whole list of names only andblock-paste over a series of skeleton DCLs. I can block-copy a series ofdata types and lengths in the same way from a RPG DS and block-pasteover a different DS; that helps ensure that the two DSes have the samedefinition. (This is most useful when I copy/paste between sessionswhere a LIKEDS isn't meaningful.)

In short, block-copy generally involves a block of characters ratherthan whole lines. However, when I use it, it's available through theiSeries Access emulator and not through any special feature of SEU.Block-copy can be done in WDSC, but it's always seemed cumbersome to me.


Tom Liotta