iSeries Navigtor Tip : Running a CL Command

[FaStOnE]

Did you know you could run CL Commands from the "Run SQL Script" screen?

Try This:

From the SQL Script Screen in iSeries Navigator --

Type:

CL:DSPOBJD OBJ(<Lib>/<FileName>) OBJTYPE(*FILE) OUTPUT(*OUTFILE) OUTFILE(QTEMP/FILELIST);

SELECT *
  FROM QTEMP.FILELIST; 

Then Highlight and press Ctl-Y or click on Run. This will show you the Object Descriptions of the DSPOBJD output and allow you to work with it.

[bryce4president]

Re: iSeries Navigtor Tip : Running a CL Command

I actually just saw this for the first time last week. But since I try to avoid CL in coding I mostly just ignored it But I can see how your example could be useful

[Denny]

Re: iSeries Navigtor Tip : Running a CL Command

Here is a good example

cl: DSPOBJD OBJ(pwc/*ALL)        
        OBJTYPE(*ALL)             
        OUTPUT(*OUTFILE)          
        OUTFILE(QTEMP/DSPOBJ)     
        OUTMBR(*FIRST *REPLACE);  


SELECT ODLBNM "Library", ODOBNM "Object", ODOBTP "Type", ODOBAT "Attribute", ODOBTX 
 "Description",odobow "Owner",oducnt "# Used" ,
date(case when substr(ODcDAT,5,2)>40 then '19' else '20' end 
||substr(ODcDAT,5,2) || '-' || substr(ODcDAT,1,2) || '-' || substr(ODcdAT,3,2)) "Created" ,
date(case when substr(ODlDAT,5,2)>40 then '19' else '20' end 
||substr(ODlDAT,5,2) || '-' || substr(ODlDAT,1,2) || '-' || substr(ODldAT,3,2)) "Changed" ,
date(case when substr(ODuDAT,5,2)>40 then '19' else '20' end 
||substr(ODuDAT,5,2) || '-' || substr(ODuDAT,1,2) || '-' || substr(ODudAT,3,2)) "Used" ,
date(case when substr(ODtDAT,5,2)>40 then '19' else '20' end 
||substr(ODtDAT,5,2) || '-' || substr(ODtDAT,1,2) || '-' || substr(ODtdAT,3,2)) "Used Reset"
FROM qtemp/dspobj ORDER BY "Used" asc  ;

[B.Hauser]

Re: iSeries Navigtor Tip : Running a CL Command

Did you know you could run CL Commands from the "Run SQL Script" screen?

Beginning with one of the last relases (6.1 or 7.1 I can't remember which one) it is even possible to include CL commands in this way in source members and run them through RUNSQLSTM.

Birgitta

[MichaelCatalani]

Re: iSeries Navigtor Tip : Running a CL Command

Beginning with one of the last relases (6.1 or 7.1 I can't remember which one) it is even possible to include CL commands in this way in source members and run them through RUNSQLSTM.

Birgitta

Every time I try to kill CL, IBM goes and updates the thing to make it more interesting.

Seriously, CL has almost received more updates in the past few releases than RPG.

[K2r400]

Re: iSeries Navigtor Tip : Running a CL Command

Beginning with one of the last relases (6.1 or 7.1 I can't remember which one) it is even possible to include CL commands in this way in source members and run them through RUNSQLSTM.

it's 6.1

[kitvb1]

Re: iSeries Navigtor Tip : Running a CL Command

Hey Jamie...
Now we can do CL in even more places

[chrisr]

Re: iSeries Navigtor Tip : Running a CL Command

@#%@#%@#%@#% I could have looked cleverer years ago

I often use this to repeat tests. Use SQL to set a value in a file then use the CL: syntax to call my RPG program and do some processing. Then use SQL to query the results. Nice and simple then to rerun the steps over and over quickly.

As an idea...

update myFile set myQty = 0 where myType = 'A';
cl: call myProgram ('A' '2010');
select sum(myQty) from myFile; 

I read CL as Command Line rather than Control Language so that is the way I thought of it. Makes it just a little bit more acceptable to use .

There are some examples in the Run SQL drop down examples list which clued me on to using this ages ago.

/* Display Dependent Files */
CL: DSPDBR FILE(library1/table1) OUTPUT(*OUTFILE) OUTFILE(qtemp/dspdbr);
SELECT * FROM qtemp.dspdbr;

/* Display Program References */
CL: DSPPGMREF PGM(qtemp/(*ALL)) OUTPUT(*OUTFILE) OBJTYPE(*ALL) OUTFILE(qtemp/dsppgmref);
SELECT * FROM qtemp/dsppgmref;