Either in memory on in NSH/tmp most likely – why ? I’m not sure if you’d be able to short-circuit it if it’s too big.
The reason for this is that the file that gets emailed gets too big. A file with 18 servers is 2MB, so imagine a file containing 200. Is there a way to edit the list that gets sent to rather just send what patches are missing an not a whole report with whats installed and whats missing?
Do you have BDSSA Reports installed in your environment?
If so, I would recommend scheduling a report to run and send the html link to users instead of emailing the raw results from the BSA job run. BDSSA Reports also allows you to send out the report in other formats like pdf and excel if required.
This is an option I thought about, but there seems to be a bit much involved in this scenario. Basically there about 10 patch admins that look after certain servers in the environment. Each month they need to patch their relevant servers. Now what they do it run a patch analysis and to see what patchees need to be deployed, they then deploy the patches and run another analysis after the install to make sure the patches have been installed correctly. Now if we had to set this up in BDSSA the etl would have to run numerous times and can get confusing because there are no set times that the patches get rolled out. So it would be easier just rather just use the email that gets generated after the analysis.
there's no way to edit what's in the email.
you could have another job or script that runs and either runs the analysis directly or looks at the last result then runs some blcli, exports the result to a file, zips it, then mails it off, or processes it and mails it off.