Skip to main content

We’re trying to implement alerting around the service that loads work into PSO daily. To do this, we’d like to better understand what an internal ID of 0 represents. In some cases, it seems to indicate success (e.g., when creating unavailabilities), while in others, it suggests a failure (e.g., when bad data is loaded into PSO).

We've noticed that PSO returns a 0 after our daily loads when a record results in a duplicated key (bad data). Are there any other reasons why a LOAD to PSO might return a 0 besides this scenario?

Hi Luis,

Please see the accepted answer on this post, it provides some information on what the return value means. 

 PSO - Scheduling API async responses | IFS Community

If there are any more questions, please let me know.

Thanks,

Kai

Hi Luis,

From the post above

“A return value >= 0 indicates that the data has been successfully processed. For scheduling data in particular, if the value is > 0 this is the internal id of the inserted data, so the data as a whole must have been processed successfully.

It is still possible however that there could be issues with some individual rows within the data, which wouldn’t necessarily cause the data as a whole to fail. Depending on the exact nature of the error, these should be reported as either warnings or errors in the event logs, either in the Input Manager event log or the DSE event log. For the example mentioned where the resource id was invalid, this issue will only be picked up and reported by the DSE once it processes the data. This clearly can’t be reported back in the Gateway response, since it may be some time after the data has successfully entered the database that the DSE picks it up.”

Any questions let me know,

Thanks,
Kai

Reply


Terms & ConditionsCookie settings