Whisper Programmer Studio

Programmer Studio - FAQ's
The powerful integrated visual development environment for server based programming.

Compiled below is a list of the most commonly asked questions answered by our technical support staff. Before contacting support, please check the FAQ's listed to see if your question hasn't already been answered.

Question and Answer Index:

What is Programmer Studio ?
The project wizard is unable to connect to the server, what's wrong ?
What is Windows Common Control Library (comctl32.dll) ?
How can I update the Windows Common Control Library (comctl32.dll) ?
Why are the errors generated by my compiler not being highlighted ?
Why are errors from the MPE/iX COBOL compiler still not highlighted ?
I am getting an error when restoring WTRSHS on MPE, what's wrong ?

Questions and Answers:

Q: What is Programmer Studio ?
A: Programmer Studio is powerful integrated visual development environment for server based programming. It combines an integrated code editor, project oriented development model and one-click compile and error highlighting.

Q: The project wizard is unable to connect to the server, what's wrong ?
A: Firstly check that the server software is installed and running and confirm which port it is listening on. If you have not changed the server configuration file, the default port number is 11000. Next, check that you can ping the server by typing PING <address> at the DOS prompt (the address can either be an IP address or DNS name). Finally confirm the user name (and password) you are using with your system administrator - remember user information is usually case-sensitive.

Q: What is Windows Common Control Library (comctl32.dll) ?
A: The Windows Common Control Library (comctl32.dll) is a system library file from Microsoft that implements the Windows standard toolbar, tab control, progress meter, and other controls. For more information on updating comctl32.dll see How can I update the Windows Common Control Library (comctl32.dll) ?

Q: How can I update the the Windows Common Control Library (comctl32.dll) ?
A: An up-to-date version of the Windows Common Control Library is included with both Windows 98 and Internet Explorer 4.0 and above. If you don't have either of these installed and you have not already upgraded the Common Control Library yourself, you can download an updated version of this library from Microsoft's Personal Support Center Page.

Q: Why are the errors generated by my compiler not being highlighted ?
A: Programmer Studio uses Compiler Output Masks to identify errors and warnings in the output generated programming language compilers. When a new project is created it has no active Compiler Output Masks, these need to be selected in the project properties.

1. From the project tree view, select the project icon.
2. From the project menu, select Settings (ALT+F7).
3. Select the Build/Compile tab.
4. From the compiler output masks list, select the compilers being used.

Compiler output masks will work with the majority language compilers as long as the output from the compiler includes the filename and line number of any errors/warnings it generates.

Q: Why are errors from the MPE/iX COBOL compiler still not highlighted ?
A: Unfortunately neither the standard COB85XL command file or the COBOLII compiler include the name of the file currently being compiled. This results in errors being generated without a filename to relate them to. There are three possible solutions to this problem:-

1. Create a new command file containing the following lines:
parm text
echo SOURCE FILE:![finfo( '!text', 1 )]
COB85XL.PUB.SYS !text

2. Modify COB85XL.PUB.SYS, adding the line echo SOURCE FILE:![finfo( '!text', 1 )] before the line which starts run COBOL.PUB.SYS...

3. Modify the Advanced properties for each file compiled, enter SOURCE FILE: $(FilePath) in the Precompile output box.

Q: I am getting an error when restoring WTRSHS on MPE, what's wrong ?
A: This error occurs if the either the incorrect file was transferred to the server or the correct file was transferred with the wrong transfer options. For example, if you are using WRQ Reflection file transfer, check you have transferred the file wtrsh-mpeix.wrq with the LABELS transfer option. If you are using Minisoft MS92, check you have transferred the file wtrsh-mpeix.ms92 with the Save File Info box checked. If you are using FTP check you have transferred the file wtrsh-mpeix.bin as binary.