topic Re: T4 Stop and collect in CSV in Operating System - OpenVMS

T4 Stop and collect in CSV

Paul Janssen — Mon, 26 Mar 2007 10:23:41 GMT

I need to reboot the server because of a problem with ftp. I did not do an abort on T4. I ended up with the following files:

Directory DKF0:[000000.T4$DATA]

T4_V3400_23MAR2007_0001_2359_FCM.DAT;1
T4_V3400_23MAR2007_0001_2359_LCK7.CSV;1
T4_V3400_23MAR2007_0001_2359_MON.DAT;1
T4_V3400_23MAR2007_0001_2359_NETM_EIB0.CSV;1
T4_V3400_23MAR2007_0001_2359_SUBP_EIB0.LOG;1
T4_V3400_23MAR2007_0001_2359_SUBP_FCM.LOG;1
T4_V3400_23MAR2007_0001_2359_SUBP_LCK7.LOG;1
T4_V3400_23MAR2007_0001_2359_SUBP_MON.LOG;1
T4_V3400_23MAR2007_0001_2359_SUBP_TCP.LOG;1
T4_V3400_23MAR2007_0001_2359_SUBP_XFC.LOG;1
T4_V3400_23MAR2007_0001_2359_TCP.CSV;1
T4_V3400_23MAR2007_0001_2359_XFC.CSV;1

Total of 12 files.

How can I convert them into CSV's and end with a ..._COMP.CSV or - if not possible - with at least as much CSV's as possible?
Then I could also look at my ftp problem.

Re: T4 Stop and collect in CSV

Martin Vorlaender — Mon, 26 Mar 2007 12:48:27 GMT

Paul,

look into T4$SYS:T4$COLLECT.COM, at the code following the label 'Post_Process_the_Data'. It's there that T4 extracts monitor data and glues things together.

HTH,
Martin

P.S.: the existance of FibreChannel monitor data leads me to the assumption that you're using at least T4 V3.4 where the above holds.

Re: T4 Stop and collect in CSV

Andy Bustamante — Mon, 26 Mar 2007 14:47:13 GMT

Look for a "T4_now.com", you can use that as a guide for the processing that needs to happen on these files.

Andy

Re: T4 Stop and collect in CSV

John Gillings — Mon, 26 Mar 2007 20:29:35 GMT

Paul,

By default, the T4 collection job is supposed to have been submitted with /RESTART. It keeps track of where it was up to. In theory should do the post processing for you.

If not, find the label referred to before, walk through the procedure and define all the relevant local symbols interactively. You can then copy and paste the commands from the procedure into your interactive session to post process the files.

Another alternative. If you know the parameters used to invoke the original job, you can trick it into thinking it's restarting with a jacket procedure:

TRICKT4.COM
$ $RESTART="TRUE"
$ BATCH$RESTART="Post_Process_the_Data"
$ @T4$SYS:T4$COLLECT parameters...

$ SUBMIT TRICKT4

Re: T4 Stop and collect in CSV

Paul Janssen — Tue, 27 Mar 2007 09:45:48 GMT

I looked in T4$COLLECT and T4$NOW and found the way it behaves.
I extracted what I needed into a once-off com file:

$ Set Command T4$Sys:T4$Mon_Extract
$!
$ T4Extr T4_V3400_23MAR2007_0001_2359_MON.DAT -
/Csv=T4_V3400_23MAR2007_0001_2359_MON.CSV -
/Process_Name=("*LMD0*","*SHAD*","*PRODOPER*")
$!
$ Set Command T4$Sys:T4$Fc
$!
$ T4FcMon Extract -
/Input=T4_V3400_23MAR2007_0001_2359_FCM.DAT -
/Csv=T4_V3400_23MAR2007_0001_2359_FCM.CSV
$!
$ Set Command T4$Sys:T4$ApRc
$!
$ T4Aprc T4_V3400_23MAR2007_0001_2359_FCM.CSV T4_V3400_23MAR2007_0001_2359_MON.CSV
$ T4Aprc T4_V3400_23MAR2007_0001_2359_LCK7.CSV T4_V3400_23MAR2007_0001_2359_MON.CSV
$ T4Aprc T4_V3400_23MAR2007_0001_2359_NETM_EIB0.CSV T4_V3400_23MAR2007_0001_2359_MON.CSV
$ T4Aprc T4_V3400_23MAR2007_0001_2359_TCP.CSV T4_V3400_23MAR2007_0001_2359_MON.CSV
$ T4Aprc T4_V3400_23MAR2007_0001_2359_XFC.CSV T4_V3400_23MAR2007_0001_2359_MON.CSV
$!
$ Rename/Log T4_V3400_23MAR2007_0001_2359_MON.CSV T4_V3400_23MAR2007_0001_2359_COMP.CSV
$ Delete/Log T4_V3400_23MAR2007_0001_2359_MON.CSV;*
$!
$ EXIT
$

This worked well for me.
Thx