Hello good afternoon!
About Script Vbs. I would like to know if when we use the SM37 transaction and we have more than 4 jobs with active status, and to the point that it becomes completed, can you put a time or command that does not hang in the processing of the VBs Script, because it ends up not waiting processing and stops recording.
Ideally, the Scripts run by taking them to the Spool and saving the file in csv, and come back to get the next one that was ready in the processing queue with status completed.
But it hangs due to speed and we can't automate via Background via Script Vbs.
Ideally, the Scripts run by taking them to the Spool and saving the file in csv, and come back to get the next one that was ready in the processing queue with status completed.
But it hangs due to speed and we can't automate via Background via Script Vbs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.