FRL Offset Determination….

[Tom Rioux]

We have a huge FRL defined in our Cloverleaf.   Occasionally we need to filter based on a certain field defined inside the FRL.  We need to determine the offset and length of the field to know what to plug into our filtering scripts.

Does anyone have a script written where you can pass the FRL and field name as arguments  and it will return to the offset within the FRL?

Thanks…

Tom Rioux

Topic

[James Cobane]

Thomas,

We have some procs that filter based on a field using the FRL definition, not determining the offset from the definition.

[Tom Rioux]

Thanks Jim!   I have taken a look at your proc and I see it uses the grm commands.   We are trying to steer clear of grm commands.   We have procs that do our filtering for us for an FRL, but we pass arguments for basically the beginning and ending offset (i.e.  BEGIN 135 END 148).  

The way we determine those values is a little cumbersome.   I thought maybe someone had something written to determine the offset and length based on arguments passed to the script/proc.

Thanks….

Tom Rioux

[Russ Ross]

We have an argument driven proc called tps_msg_action proc that is oftened used here to KILL a message based on content of a buried filed, but I’m pretty sure it uses grm.

I have come to question if grm is as awfull as I was first lead to believe.

Russ Ross
RussRoss318@gmail.com

[Tom Rioux]

We were seeing performance issues caused by the use of grm in some of the older procs that were in place.   We have re-written most of the procs that utilize grm except for a couple.  

I would like to do this without utilizing grm.   I’m sure it can be done and I’ll figure it out.

Thanks Russ and the 2 Jim’s!

[Russ Ross]

I will keep that in mind with regards to is grm bad.

I’m sure what you want to do can be done, I just don’t think I have a proc like that lying around but suspect someone out there does.

Russ Ross
RussRoss318@gmail.com

[Author]

Replies