DSXchange

cat will work in an Information Server 8.1 installation on Windows. The MKS toolkit which is installed with IS provides many Unix commands, including cat.

Regards,

Oh ok. Thank you.

In DOS it's "type".

Thanks for the correction chulett.

But cat will work, as noted. Or, particularly if the first check is done in a server job (which I recommend as best practice when only one row is being processed), the count can be placed in that job's user status area and retrieved using the $UserStatus activity variable of the Job activity.

ray.wurlod wrote:But cat will work, as noted.

Of course, just noting what the DOS equivalent would be.

Another possibility is:
Build a new Server-Routine UpdateUserStatus (or whichever name you prefer) with the following code:

Call DSSetUserStatus(Arg1)
Call DSLogInfo(Arg1,'UpdateUserStatus')
Ans = Arg1

The routine writes its input to the variable UserStatus of a ServerJob (cannot be used in PX-jobs) as a string - and to the job log (just for informational purposes).

Now build a simple ServerJob which runs the above query and passes its result to a Dummy-Output-Column of a transformer with the derivation UpdateUserStatus(<<Input-Column-from-Query>>). On Unix-Systems you can send the result to /dev/null using a Sequential-File-Stage.

The Sequence looks as follows

ServerJob_with_UpdateUserStatus -- Control Email notification Or Execute depended Job. Use two links with Custom triggers and evaluate Activity-Variable ServerJob_with_UpdateUserStatus.UserStatus to manipulate the logic according to your requirements.

No writing and reading files involved. Nothing to cleanup afterwards.

You can also use this to pass an array of semicolon separated parameters to subsequent jobs in a sequence, which can afterwards be split using the field() function.