(imported topic written by ajandi91)
First I’d like to say this forum rocks, a lot of great people and advice. I have a question and hope this is correct place to post it. THANKS FOR ALL YOUR TIME IN ADVANCE.
I have a task running to capture the AIX system firmware versions from our 400+ LPARS (210 Frames) which ran fine and produced results that I can have my management, SA’s etc… run reports on to determine how we’re progressing on our infrastructure wide initiative to get all frames upgraded to SF240_403.
The ISSUE: The capture is no longer working, we have upgraded over 75 frames and confirmed this at the CLI/Via the HMC. The data in BF is not changing and we have changed the scheduling to run the task 1 a day from bi weekly and before that weekly.
What the task is running is a simple shell out running the lsmcode command:
not sure if the task action is wrong or the analyses parsing data into BF is issue or neither. Need help as I’m new to BF.
Sorry forgot to mention we’re on 8.1
- THIS IS THE ORGINAL ACTION THAT WORKED TO PRODUCE DATA ###########
(version of client >= “6.0.0.0”) AND (exists true whose (if true then (exists (operating system) whose (it as string as lowercase contains “aix” as lowercase)) else false))
Action:
delete __appendfile
delete /tmp/task_lsmcode.sh
appendfile #!/bin/sh
appendfile lsmcode > {pathname of parent folder of client}/task_lsmcode.log
move __appendfile /tmp/task_lsmcode.sh
wait /bin/sh -C /tmp/task_lsmcode.sh
- THEN WE ADDED THIS TO IT ############
we added: delete /tmp/task_lsmcode.log
our thinking was the log file was being appened to and new data via lsmcode was not being parsed. so to create a new file each time.
- THIS IS THE NEW COMMAND WE’RE THINKING OF USING ##########
delete __appendfile
delete /tmp/task_lsmcode.sh
appendfile #!/bin/sh
appendfile lsmcode > {pathname of parent folder of client}/task_lsmcode.log
move __appendfile /tmp/task_lsmcode.sh
run chmod 755 /tmp/task_lsmcode.sh
wait /bin/sh -C /tmp/task_lsmcode.sh
Thanks
Andre