Try this little snippet: " strip trailing blank |", " joincont leading / / |",
A little SPEC to follow for putting things into columns should follow. Good Luck. ==>-----Original Message----- ==>From: CMSTSO Pipelines Discussion List [mailto:CMS- ==>[email protected]] On Behalf Of Jeff Henry ==>Sent: Tuesday, June 30, 2009 2:39 PM ==>To: [email protected] ==>Subject: Joining lines when some are split. ==> ==>Hello, ==>I'm trying to process a report which is the output of CA-EPIC's catalog ==>listing. Most of the detail lines of the report look like the first line ==>below, with the dataset name followed by the volser and other information ==>all on one line. However, if the dataset name is longer than 17 ==>characters, ==>it will be split like the second and third lines below, so that the dsn ==>is ==>on a line by itself, followed by the rest of the information on the next ==>line. ==> ==>Z0926.LIB.BKUP SS0017 2 1 Z0926 01/06/05 ==>BACKUP.POST.REFRESH.EPIC ==> SS0037 1 1 BACKUP 05/17/04 ==> ==>What I'd like to do is get these all into the same format while keeping ==>everything lined up. Something like this: ==> ==>Z0926.LIB.BKUP SS0017 2 1 Z0926 01/06/05 ==>BACKUP.POST.REFRESH.EPIC SS0037 1 1 BACKUP 05/17/04 ==> ==>I've been trying to get something working using SPEC with an IF and a ==>READ ==>but I can't get it to work right. Not quite sure how to know when I need ==>to ==>READ that second line. Or maybe SPEC is the totally wrong approach. ==> ==>Any advice? ==>Thanks, ==> ==>-- ==>Jeff Henry
