So Joel, what's the issue with DOCSQL ?
It does create a source member in QTEMP, but I don't see that as a PCI issue since only that job has access to the source and you can delete the temp file immediately after running the SQL if needed.
You can use RUNSQLSTM, but I believe that needs a source member as well.
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
date: Thu, 29 Mar 2012 14:13:13 +0000
from: "Stone, Joel" <Joel.Stone@xxxxxxxxxx>
subject: RE: Is there a better way to run SQL in a CL pgm?
Just curious - what IS acceptable in your shop? Placing SQL stmts in a source member? Other methods?
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Thursday, March 29, 2012 8:51 AM
To: Midrange Systems Technical Discussion
Subject: Re: Is there a better way to run SQL in a CL pgm?
Note that in our shop...
Doing dynamic SQL like this means and automatic failure of our Secure
Code Review as required for PCI compliance...
Unless RJS's DOCSQL doing something other than what I assume it does...
On Wed, Mar 28, 2012 at 12:05 PM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:
To do this in CL gets a bit messy with the single-quotes, 2x single quotes, etc.
I am using the RJS software command DOCSQL.
Does IBM provide an SQL interface for running in directly in CL similar to what is shown below?
(without storing commands in a source file member?)
Any idea why they dont?
Is there a better way to do this in CL?