Is there a more elegant way to determine if a spool file requires this
processing, as opposed to what I'm doing which is running NETDATA command and
if RC==0 then it's net data.
e.g.
"PIPE CMS NETDATA QUERY | VAR NETINFO"
If RC==0 then /* Did it work? */
(process as NETDATA)
else
(normal process)
Also, does anyone know what the first two bytes of a (filetype of) CONLOG is?
TOF:
4D8B5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C
5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C
( " * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * *
5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C4040
* * * * * * * * * * * * * * * * * * * *
4D8B5C40 4040D396 8740A2A3 8199A385 84409695 40F2F0F1 F261F1F1 61F0F440
81A340F0 F07AF0F0 7AF0F040 40404040 40404040 40404040 4040
( " * L o g s t a r t e d o n 2 0 1 2 / 1 1 / 0 4 a t 0
0 : 0 0 : 0 0
4040 40404040 40404040 40404040 40404040 405C4040
*
4D8B5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C
5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C
( " * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * *
5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C5C5C 5C5C4040
* * * * * * * * * * * * * * * * * * * *
EOF:
First byte could be a length byte (4Dx = 77).
Frank M. Ramaekers Jr.
> -----Original Message-----
> From: CMSTSO Pipelines Discussion List [mailto:CMS-
> [email protected]] On Behalf Of Mike Walter
> Sent: Friday, August 17, 2012 10:21 AM
> To: [email protected]
> Subject: Re: [CMS-PIPELINES] READER stage
>
> Indeed. That file is in NETDATA format, the format created by the SENDFILE
> command in CMS and the TRANSMIT command on TSO.
>
> Will Roden wrote and shared a NETDATA REXX stage to help process NETDATA
> reader files, which I'll post below.
> There may be other ways to handle it, and probably some newer ones, but
> this works quite well.
>
> Mike Walter
> Aon Corporation
> The opinions expressed herein are mine alone, not my employer's.
>
> /* CFORUM: PIPESAMPLES on YC2VM, downloaded 10/10/95 by mrw
> /*Appended at 02:05:00 on 93/07/16 GMT (by RODEN at GDLVM7) */
> /*Subject: NETDATA filter */
> /* */
> /* Here's a front-end to DEBLOCK NETDATA that I wrote a long time*/
> /*ago because I was sick of looking up formats every time I used it.*/
> /* */
> /*NETDATA PREP removes the control characters from SPOOL file recs. */
> /*NETDATA DISK untangles the NETDATA format. */
> /*NETDATA with no parameters does both. */
> /* */
> /* */
> /* Glenn S. Knickerbocker, GSKNICK at FSHVMX, 19 July 1989 */
> /* quick front-end to DEBLOCK NETDATA */
> /* when you don't care about tags and such */
>
> prep = ,
> '| find' '41'x ,
> '| spec 2-* 1'
>
> netdata = ,
> '| pad 80' ,
> '| deblock netdata',
> '| find' 'c0'x ,
> '| spec 2-* 1'
>
> Arg option
> option = strip(option)
> Select
> When option = '' then process = prep netdata
> When Abbrev('PREP',option) then process = prep
> When Abbrev('DISK',option) then process = netdata
> Otherwise
> Say 'Valid options for NETDATA are PREP and DISK.'
> Exit 40
> End
>
> 'addpipe *:' process '| *:'
> /* End of file */
>
>
>
> -----Original Message-----
> From: CMSTSO Pipelines Discussion List [mailto:CMS-
> <mailto:[email protected]>
> [email protected] <mailto:[email protected]> ] On Behalf Of
> Frank M. Ramaekers
> Sent: Friday, August 17, 2012 10:13 AM
> To: [email protected] <mailto:[email protected]>
> Subject: READER stage
>
> I'm not sure how to decode the READER stage stream. If I look at it (pipe it
> to
> CONSOLE) there appears to be some prefix information:
>
>
>
> #\INMR01 â & HOSTNAME ANONYMOU HOSTNAME MAINT
> 20
>
> 1
>
> 20817150953 CMS/TSO Pipelines INMR123.>\INMR02 INMCOPY
>
>
>
> â & - ñ 20120817150953 A USERID DATA 1
> \INMR
>
> 0
>
> 3 â & ñ ê{(actual data starts here)
>
>
>
> (If I PEEK the file, it looks just fine.)
>
>
>
> Frank M. Ramaekers Jr. | Systems Programmer | Information Technology |
> American Income Life Insurance Company | 254-761-6649
>
>
>
>
> _____________________________________________________
>
> This message contains information which is privileged and confidential and is
> solely for the use of the
>
> intended recipient. If you are not the intended recipient, be aware that any
> review, disclosure,
>
> copying, distribution, or use of the contents of this message is strictly
> prohibited. If you have
>
> received this in error, please destroy it immediately and notify us at
> [email protected] <mailto:[email protected]> .
