Difference between revisions of "WDSC tips"

From MidrangeWiki
Jump to: navigation, search
m (moved Editor section to WDSC tips/Editor sub-page to get under 32K warning limit)
m (→‎COMPILE: moved content to WDSC tips/Compile to stay under 32K size warning limit)
Line 6: Line 6:
  
 
==COMPILE==
 
==COMPILE==
−
 
+
See [[{{PAGENAME}}/Compile]]
−
===RPG source was not being saved===
 
−
original post [http://archive.midrange.com/wdsci-l/200712/msg00012.html]
 
−
 
 
−
*A RPG source was not being saved to my source file.
 
−
I can see the changes in WDSCi but not in the Iseries source.
 
−
*Another symptom is when debugging I need to select the Listing View as the debugger is finding some old source for the *SOURCE view.
 
−
*I cleared the File Cache and the debug cache.
 
−
*I discovered a work around.
 
−
Say the member is PGM001, I renamed it (via WDSCI by right-click on the source and Rename)
 
−
to PGM001X, do my changes and save them.  Then I rename the member back to PGM001.
 
−
 
 
−
*But the real problem was in Iseries Projects.
 
−
I had previously saved this source in a Project so that I could do work on my home PC.
 
−
When I deleted the member from the Window/Open Perspective/Iseries Project view all worked
 
−
as expected.
 
−
 
 
−
Return to [[#TOP]]
 
−
 
 
−
===Error-messages are still showing in the edit view===
 
−
original post [http://archive.midrange.com/wdsci-l/200706/msg00409.html]
 
−
 
 
−
*After compiling, getting errors, and fixing them, and recompiling successfully, the error-messages are still showing in the edit view.
 
−
*How to get rid of them with out closing the member
 
−
#Ctrl+F5,
 
−
#or either Source>Remove Errors,
 
−
#or Source>Refresh.
 
−
*Its on IBM's list of requirements to automatically remove these during error list reloads.
 
−
*Remove messages from the source by choosing SOURCE/Remove Messages from the top of the screen.
 
−
*While you have theError List window open,
 
−
#click on the triangle in the top right corner of the window,
 
−
#choose Show Severity
 
−
#and uncheck Information to not show informational messages.
 
−
*From the same menu,
 
−
#click Messages,
 
−
#choose Insert Selected Only.
 
−
This will only insert the message you click on from the Error List Window into the source, and will remove the previous error message when you choose another from the Error List Window.
 
−
 
 
−
Click the X icon in the top left part of the iSeries Error List view.  (Note: This closes the error list view, but does not clear any errors inserted in the editor window.  However, it is important to remember that the errors are not made a part of the source itself.  They are simply shown in the LPEx editor window.)
 
−
 
 
−
Return to [[#TOP]]
 
−
 
 
−
 
 
−
===SQLRPGLE Compiles how to find Compile errors ===
 
−
original post [http://archive.midrange.com/wdsci-l/200602/msg00196.html]
 
−
 
 
−
* First turn off Batch compiles (see compile [[WDSC tips#Within RSE, how to compile Interactively versus Batch|Interactively]] tip)
 
−
* Next select Compile(Prompt) to see the compile Parms
 
−
* Select CRTSQLRPGI
 
−
* Click All Parameters checkbox.
 
−
* Set the 'To source file parm to QSQLSRC in 'your lib' NOT QTEMP.
 
−
The compile will retreive the EVENTS file and show messages in the Iseries Error list View.
 
−
 
 
−
You can click on the error and the source will be displayed with the cursor positioned on the error, but be careful as to what source member is in the 'Location' column of the Iseries Error List view.
 
−
 
 
−
If the QSQLSRC member is listed you need to open the 'real' source to the same position to do the appropriate correction. 
 
−
 
 
−
Ctrl-L lets you jump directly to a given line, or you can type the line number in the Editor command line and you go directly to the line.
 
−
 
 
−
Should you find Compile(Prompt) to be a pain, you could customise the compile command.
 
−
*In Table View, Right Click a Source,Click Compile , Click Work with Compile commands
 
−
*Select CRTSQLRPGI and Click Edit
 
−
*Add  TOSRCFILE(&L/QSQLSRC) to the command, this saves you setting this parm all the time.
 
−
 
 
−
 
 
−
FWIW
 
−
*I found some notes on SQL Restrictions
 
−
*In WSDC V6 Open the CODE editor
 
−
*Click Help,General Help
 
−
*Enter 'Code Tips SQL in RPG and Cobol'  Click GO
 
−
*Click 'CODE Tips and Techniques - SQL in RPG and COBOL '
 
−
*Read 'There are some restrictions you should be aware of:
 
−
 
 
−
Return to [[#TOP]]
 
−
 
 
−
===Within RSE, how to compile Interactively versus Batch===
 
−
original post [http://archive.midrange.com/wdsci-l/200309/msg00028.html]
 
−
 
 
−
*Window -> Preferences -> Remote Systems -> iSeries -> Command execution
 
−
 
 
−
There is a compile in batch check box.  Uncheck that because the
 
−
compile still draws from the Batch CPW of the server.
 
−
 
 
−
Return to [[#TOP]]
 
−
 
 
−
 
 
−
===Custom Compile Commands===
 
−
 
 
−
====Synopsis====
 
−
In order to have WDSC automatically bring up the compile error list when you are using custom compile commands:
 
−
*Add {{code|OPTION(*EVENTF) SRCMBR(&N)}} to the end of your compile command.  This tells WDSC that the command being executed is a compile command.  Note that if you have a custom compile command that does not have these parameters, you can append them as a comment: {{code|/* OPTION(*EVENTF) SRCMBR(&N) */}}
 
−
*Make sure that you are setting a *CURLIB.
 
−
*For OPM compilers, use {{code|OPTION(*LSTDBG)}} or {{code|OPTION(*SRCDBG)}} to trigger creating the event file.
 
−
 
 
−
 
 
−
====Supporting posts====
 
−
original post [http://archive.midrange.com/wdsci-l/200712/msg00089.html]
 
−
 
 
−
How to get the error list back into WDSC
 
−
*Make sure that you are setting a *CURLIB.  This is very important, because that's how the UI finds the EVFEVENT file generated by the compiler. 
 
−
[http://www-1.ibm.com/support/docview.wss?rs=3239&context=SSZND2&dc=DB520&dc=D600&dc=DB530&dc=D700&dc=DB500&dc=DB540&dc=DB510&dc=DB550&q1=compile&uid=swg21231854&loc=en_US&cs=utf-8&lang=en Technote 1231854] from ibm.com describes the official IBM help on the subject. 
 
−
* [[WDSCi_troubleshooting#I_have_a_custom_compile_command.__How_do_I_get_the_error_list_back_into_WDSC.3F|WDSCi Troubleshooting]] points here.
 
−
 
 
−
Nazmin adds this: [http://archive.midrange.com/wdsci-l/200712/msg00111.html]
 
−
*If you are running your compile commands from CL, the Error List View is not automatically opened to populate the errors.
 
−
*However, if you specified an option to generate the events file, say for OPM compiler {{code|OPTION(*LSTDBG)}} or {{code|OPTION(*SRCDBG)}}, an event file containing the errors is generated.
 
−
*You can manually open this events file in the Error List view and proceed normally.
 
−
*To locate the events file, look in the target library for the compile command for data file EVFEVENT.
 
−
*If you expand this file, you will see all the events files, with the same name as the source member and type mbr. Right click on this, choose the option to Show in Error List.
 
−
 
 
−
Andrew adds this: [http://archive.midrange.com/wdsci-l/200712/msg00115.html]
 
−
*You can code your own Compiler command, which can then be used to determine which command to run, based on the source member type (you have to write your own code here to retrieve the source type).
 
−
*That will then run the command in question, i.e. CRTSQLCBL, CRTCICSCBL, etc.
 
−
*Your own command has to have a parameter called OPTION, that will accept *EVENTF or *NOEVENTF. The parameter doesn't have to do anything, but it needs to be there.
 
−
 
 
−
*When {{code|OPTION(*EVENTF)}} is specified, WDSC will look in the first 20 bytes of the *LDA. This must contain the library and member for the compiled source, so your compiler front end needs to ensure that the *LDA is correctly populated.
 
−
*Assuming that the *LDA is correct and that your IBM supplied compiler command (called by your front end) has been called with {{code|OPTION(*EVENTF)}} - WDSC will then automatically retrieve the correct event file and switch to that tab in the table view.
 
−
 
 
−
*Depending on your settings, this will also insert the error messages into the source member in the Editor.
 
−
 
 
−
*I spent a fair amount of time going through this, and found the following IT Jungle article invaluable [http://www.itjungle.com/fhg/fhg080404-story01.html] when creating our internal version for WDSC.
 
−
 
 
−
Return to [[#TOP]]
 
  
 
==FIND ==
 
==FIND ==

Revision as of 15:01, 29 February 2008

This is a dump of tips gathered from the WDSCI-L list.

EDITOR

See WDSC tips/Editor

COMPILE

See WDSC tips/Compile

FIND

Scan for a date when source lines were changed (like F14 in SEU)

original post [1]

  • You could issue the "locate sequenceText" command (in the command line at the case of the RSE editor or press ESC to enable command line), then invoke it repeatedly from the LPEX command line (UP arrow key, Enter).
  • example locate sequenceText 071201 to 071231
  • You can filter by date. Right-click in the source and you can filter by date. ref [2]

Locate is an Editor command.

There is more find info at WDSC Find Tips

Return to #TOP

Find Tips

original post [3]

Check WDSC Find Tips

Check Searching for text

  • In WDSC
  • Click Help,
  • Click Help contents
  • Search on 'Regular Expression Grammar',
  • click on 'Regular Expression Grammar to see ALL the codes.
  • This is very useful when you tick the 'Regular Expression' check box in the LPEX Editor EDIT,Find/Replace.

Return to #TOP

Find Field usage (for SQL where OUTLINE doesnt work)

original post [4]

  • To see where a field is used,
  • double click (select) the field name,
  • then right click, Selected->Filter Selected.
  • If you're command-line oriented, you can do the same thing with 'findText all field_name'
  • Ctrl-W to go back to the normal view or 'expandAll on command-line

Return to #TOP

DEBUG

Debug and SEP Service entry prints

original post [5] (the post contains a lot of other information)

  • In Iseries Table View
  • Right Click on the Source
  • Select Debug(service Entry)/Set Service Entry Point
  • Next Panel Click OK (I have not done Service Programs)
  • If you get a 'Iseries Debug Message has not been started yet' message, follow the instruction, then try again.
  • When the SEP is is set click OK.
  • Run the program, however you normally would, eg. call, menu option, whatever.
  • You need to run the program under the User Profile in the SEP
Check Service Entry Point, if you need to change the user profile of the SEP.
  • The WDSC Debug view should pop up and you can set breakpoints view variables etc. etc. check Interactive Debugger

Return to #TOP

Clear Breakpoints

original post [6]

  • In the Debug perspective
  • Click the Breakpoints tab
  • There is an icon, (looks like a double X) to remove all Breakpoints

You can manage ALL of your breakpoints across multiple programs and multiple languages, both on the client and on the server. You can enable and disable them, as well as remove them entirely.

Return to #TOP

Field Values

original post [[7]]

  • Window -> Preferences -> Run/Debug -> Compiled Debug
  • Check Tick, 'Always use Debugger Editor while debugging'

FWIW I also Check Tick

  • Allow hover evaluation
  • Double-Click in Debugger Editor to add monitored expression
  • Centre view on execution line

(FKOL 21:17, 4 February 2008 (CST))

In V6.0, the debugger started to use iSeries Editor as the default editor to display the source. The fly over expression evaluation was available in OPM RPG, ILE RPG and ILE COBOL.

Return to #TOP

Debug Breakpoints not breaking

original post [[8]]

When Debugging also when debugging SQLRPGLE

  • Use listing view
  • Turn off all caching. Window -> Preferences -> Remote systems -> File Cache, ______ Click 'Clear cached files'
  • Window -> Preferences -> Remote systems -> iSeries -> Cache, ______ Check 'disable caching' and click on the 'Clear cache' button.
  • Refresh the table view often, especially before setting the SEP.

Return to #TOP

SETUP

User Actions

Check User Action

Return to #TOP

What are Profiles and Filter Pools for

Check Profiles, Connections, and Filters

Check RSE filter

Return to #TOP


Remap Keyboard Shortcuts

Check remap shortcuts

Check WDSC shortcuts

Return to #TOP

Other Language Setup (Japanese)

original post[[9]]

The assumption made is that your PC is set up to your preferred languange and the fonts are available on the PC.

  • In Window -> Preferences -> Lpex Editor -> Appearance
  • Change the font to the appropriate language.

Return to #TOP

MISC

RSEF1002E Error

Operation failed. File system input or output error.

  • Exit WDSCi and reboot your PC.
  • I changed my password recently. For some reason my password got disabled. Also my Netserver password was disabled. (see Disabled User IDs in Netserver via Navigator.)
  • I reset my password, had my Netserver ID enabled and rebooted, all was OK.

original post FKOL 05:17, 11 December 2007 (CST)

Return to #TOP

Easy Source Upload

original post [10] (This came from the comment about copying source between systems)


  • There are lots of useful RPG sources posted on the net,
  • But , How do I get that source into my source file.

WELL WDSCi is a really simple method to upload the source.

  • Mark and copy the source you found on the net.
  • In RSE use CRTL-Shift-A to open a source member into your favourite library/file. (Member will be created if it does not exist)
  • Paste the source code and save it (CRTL-S is one way to save)
  • Voila the source is now yours!!

Return to #TOP


The outline view of the RPG (or other) program doesn't show the fields TEXT.

original post [11]

The outline view of the RPG (or other) program doesn't have any way to show the TEXT associated with the field in a file, but:-

  • You can easily open the Field Table View that does.
  • This will open the iSeries Field Table View which gives all the field information.
  1. Right-click on the line with the F-spec
  2. Select the Show fields menu option.


  • To show the properties of fields in files.
  1. Right click on a physical file object in RSE tree view
  2. and select show in table -> fields.


  • If you are using 7.0, you are also able to bring up a Field Table View by highlighting any (PF, LF, DSPF, etc...) file in an RPG program's F-Specs then select Source->Show Fields from the Menu Bar.
  • The above tips only work if the file is externally described in the F specification.

Return to #TOP

List libs, objects, members, etc with descriptions?

original post [12]

Is there a way to list libs, objects, members, etc in the Remote Systems view with descriptions?

  • The tree view doesn't support this - although if you look at the properties view - you will see the description when an item is selected in the tree view.
  • You should probably try the table view. Window>Show View>Other (or iSeries Table View)

Return to #TOP


SQL result set only contains 50 rows

original post [13]

You need to open the Data View to enable this preference.

  • Window -> Preference -> Data -> Sql Query that lets you specify the maximum number of rows to return,
  • as well as maximum bytes to retrieve for large columns.
  • The default max number of rows is 50.
  • Get V7 if you can.

Return to #TOP

I have these strange square symbols in my code.

ref PabloMotte, 27 November 2007 (CST)

When you are in RS LPEX, right-click and select Source>Hex Edit line, you will then see the hex value in the iSeries codepage, along with the client codepage.

Also, you can put the cursor on the square, press ESC (to move to the command line) and type "query hex". The "set hex 84" command will set the current cursor position to hex 84 (which turns on 'underline' for the SEU display).

  • Examples of hex codes you can use with "set hex"
    • 80 Normal
    • 81 Inverse
    • 82 White
    • 83 Inverse White
    • 84 Underline
    • 88 Red

Return to #TOP

Run a program on your PC

original post [14]

There are several programs that come with System i Access for Windows that can be interesting to use, but you can run other programs on your PC too. Those programs are wrksplf, wrkmsg, wrkprt and wrkusrj They are found in the System i Access program folder. On my default install, that is C:\Program Files\IBM\Client Access To register one of these programs in WDSC 7.0.0.x, take the following steps:

  • Run (from the menu.)
  • External Tools and then select (again) External Tools.
  • Click on the Program config once to select it.
  • Click on the New Launch Config icon on the far left (the one with the plus sign) at the top of the panel.
    • In the Main tab:
      • In the Name box I entered the name of the .exe (e.g. Wrksplf)
      • In 'Location' click 'browse file system' and drill to the exe in the IBM Client access folder and select the exe.
      • In 'Working Directory', copy & paste the path and strip off the final slash and the name of the .exe
    • In the Common tab:
      • In the middle, Display in favorites menu, select 'External Tools' and the new application will show up under Run->External tools
    • Click apply, then run to test. Close the app.

When you select Run->External Tools again it should appear at the top of the context menu. You can change the order they appear on the Run->External Tools context menu by using Run->External Tools->Organize favorites

Return to #TOP


Where can I find a list of enhancements in V7?

original post [15]

You can find the list here: [16]

How do you work through learning the functionality of this application?

original post [17]

  • Currently I'm just stumbling through the basics, and I know I'm not doing many things the most productive way.
  • I recommend that you try the tutorials included in the product as well as the PDM/SEU transition to RSE/LPEX - which was revamped and rewritten for v7.0.
  • Also, if you go to the WDSC web site [18] and search the support section - you will find additional tutorials and the labs from COMMON.
  • Don Nitke has a site with a bunch of tutorials at [19]
  • Joe Pluta adds:

You can use the help and tutorials from within the product itself. There are some free tutorials out on the web, including my own first one. You can buy my book, WDSC: Step by Step, which is based on version 5.1.2, but still pretty valid. You can buy my training course from Rochester Initiative which is now available for version 7.

  • You can go to a jumpstart at a technical conference, or an all-day standalone seminar sponsored by your local user group.
  • Or you can contract with someone to come onsite and provide training.

Return to #TOP


External links

The official WDSC web page [20]

The WDSC Developer blog [21]

WDSC tags on del.ici.ous [22]

Categories

Retrieved from "https://wiki.midrange.com/index.php?title=WDSC_tips&oldid=9660"