News

January 2004 - Customer Reporting Key, by Mike Gatiss.

This small drop down option on the basic tab of an applications properties is absolutely invaluable in debugging, especially if your print runs are usually high volume.

Whenever possible, make sure you set the Customer Reporting Key to something useful and unique, (e.g. account number) on any applications you build. This makes tracking any errors you come across much easier to trace as Dialogue will report the Customer Key along with the error message in the Messages file.

If you don't have the Customer key set, Dialogue will report any errors based on the start record of the customer in error.

e.g. without Customer Reporting Key:

EX001000T (100) ********************* Customer 100:    Starts at input
record 17256 (byte 4331005)

EX003524W (100) A reference value (1288066002) could not be found in a
reference file (Client Campaign).
 No value was set.

Not a great help, if you're working on MVS this would mean scrolling through 17256 records to get to the data causing the problems.

However with the Customer Reporting Key set to Account Number:

EX001000I (8) ********************* Customer 100: 4289762009   Starts at
input record 17256 (byte 4331005)

EX003524W (100) A reference value (1288066002) could not be found in a
reference file (Client Campaign).
 No value was set.

In this case, Dialogue has given you an account number, this allows you to do a search for the account number rather than having to scroll through the file (which on a mainframe with a 2 million record file can take a loonnnnggg time). It takes seconds to set up, but I can guarantee it will save you much more than that.

Submitted by Mike Gatiss, PrintMonkey.net

Would you like to submit an article? Check out our submissions page.

 


Main | Articles of Incorporation | Email Lists | News | Message Board

Exstream Software and Dialogue are trademarks of Exstream Software, Inc.

Exstream Software: connecting with the eGeneration Dialogue