No, it has to do with the content of the record, not with some kind of blocking.

Our monwrite writes monitor records based on it's domain and record number. In 
case of the linux mon_fsstat monwrite will write one record per mounted 
filesystem every minute. So the resulting monwrite file contains just 
individual records that needs to be processed.

A record starts with some fields of fixed length, such as TOD and userid. Next 
it has three fields of variable length, the length of each field is in front of 
the actual data. After these fields there are a number of field of fixed 8-byte 
length.

There are a few problems in this case. The first is to extract the number that 
indicates the fieldlength. Next, to calculate the starting position of each 
field. And I remembered a new problem, the number is actual a hex number, so 
before calculating it has to be converted into decimal.

To test it I'm writing a REXX stage to process the record. If possible I'll try 
to rewrite that into a specs.

Berry.

-----Original Message-----
From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On 
Behalf Of John P. Hartmann
Sent: donderdag 12 augustus 2010 11:58
To: [email protected]
Subject: Re: [CMS-PIPELINES] Processing records with variable length fields

Are you sure that deblock sf or deblock cms won't do it for you.  You then need 
to pad and gather the records with the usual deblock lineend
trick.   j.

2010/8/12 van Sleeuwen, Berry <[email protected]>:
> A rexx program is yet another file to maintain. Within specs would 
> save me from creating a separate file.
>
> I'll have a look at WHILE and record().
>
> Thanks, Berry.
>
> -----Original Message-----
> From: CMSTSO Pipelines Discussion List 
> [mailto:[email protected]] On Behalf Of John P. Hartmann
> Sent: donderdag 12 augustus 2010 11:17
> To: [email protected]
> Subject: Re: [CMS-PIPELINES] Processing records with variable length 
> fields
>
> You can format the record with SPECs using WHILE and record() to 
> extract from a moving position in the record, but whether you write a 
> specs program or a REXX program is probably eins bier.   j.
>
>

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to