I don't think this is a known problem. A good starting point is to look at the Job Log from the UI and also the appserver log.
Nothing in the Job Log in UI \or Appserver Log.
This is a Type 2 Script (Running against App server), and this used to work perfectly fine before upgrade.. I created another new Type 2 script and this is also not working.
Where as Type 1 scripts works.
This is strange, I have attached a screenshot of UI log
there are various ways to troubleshot this, you can add this line at the beginning of your NSH Script
....here comes your script content
This will output debug on the UI log.
You can also check the appserver log for any pointers and also, assuming your script runs blcli calls in the background, the blcli.log on the appserver.
The script is not being picked at all during execution.. I have all the debug set in the script.. I have been working on them since some time, but never faced such an issue.
The Job is not picking the script.. i.e. Its not reading the script at all..
I created a new TYPE 2 NSH Script (Allow RUn with No Targets) and tried to execute it, but same results.
This is a problem with 8.2 SP4, TYPE 2 Scripts without actaul Targets do not work.
A Defect has been raised (QM001782543) to fix this in 8.2 SP4.
Hi Santosh ,
is this an issue of SP4 or was it fixed with SP4 ?
It was unfortunately a problem introduced by QM001776700 in SP4
Engineering are in the process of creating a fix.
Please open a support ticket if you need the fix.
Thanks & Regards,
To understand this further, does this mean that if we have a type 2 NSH script job with no targets, but include it as part of a batch job where it inherits the targets, will the job fall over or will it work in this instance?
Type 2 scripts when executed with targets they work fine, only when you run them against app server without actual target then it is not working.
In you scenario it should not be a issue, but still check it in atest environment.
Issue has been resolved in any release from 438 (SP4 was 437) and upward.