Thanks for the input guys.
As long as I know I can consistently get the next number using the *SQL naming with a library/schema qualifier in place, this should work for my needs which is a getting back a consistent unique next number.
Normally I would use a data area and a CL program, but this is a project where I don't want to install any custom objects on the customer system outside of the next number SEQUENCE object.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
I guess I'll go with that but you would think *SYS and *SQL naming would work consistently the same.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
As an Amazon Associate we earn from qualifying purchases.