home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
gbase311.zip
/
README.1ST
< prev
Wrap
Text File
|
1995-05-25
|
37KB
|
829 lines
GUIDELINES 3.1A
───────────────
Graphical User Interface Editor and Application Generator for Personal
Computers running IBM's OS/2 Version 2.1 or higher.
JBA reserves the right to change the function and design of the
Guidelines product without prior notice.
LICENCE CONDITIONS
──────────────────
Subject to the following terms and conditions, JBA Software Products
(Ireland) Limited ("JBA") grants to you ("the User") a non-exclusive
non-transferable licence to use The Software product contained on the
media referred to by its product name "GUIDELINES", ("The Software") and
related manuals ("Documentation").
1. Scope of licence
1.1 The Software may only be used by the User to whom JBA has
directly supplied The Software.
1.2 This licence allows the User to install and use The Software solely
on a single computer processor or the specified computer processors
noted in writing on the Documentation accompanying this Software.
The User shall only install and use The Software on the number of
processors for which it is licensed, and no part of The Software shall
be reproduced or loaded into, transmitted to or used on any other
processor with the exception of runtime DLLs as listed in the
documentation.
1.3 The Software shall not be transferred, sold, assigned, leased,
rented or charged or otherwise dealt with by the User to any other
party without the prior written consent of JBA.
1.4 The User may not grant sub-licences, leases, or other rights in
The Software to others.
1.5 The User shall not alter or vary the software nor modify, merge
or combine the software or documentation with any other software
or documentation.
1.6 The User shall not copy the whole or part of The Software and/or
the documentation save as expressly permitted herein.
1.7 The User shall not reverse compile the whole or any part of
The Software from object code into source code.
1.8 The right to use provided under this licence will terminate
immediately upon breach of any condition herein. Upon termination,
the User shall immediately destroy or return to JBA all copies of
The Software and Documentation in their possession and confirm
this in writing to JBA.
2. JBA Software Rights.
The Software and Documentation is the exclusive property of JBA and
as such JBA shall, at all times, reserve copyright and other rights,
title and interest in The Software and Documentation. The User acquires
only the non-exclusive, non-transferable right to use The Software and does
not acquire any rights of ownership in The Software, the Documentation
or the media upon which The Software is embodied. This licence is not
a sale of The Software.
3. Non Disclosure; Copies; Alteration
3.1 The User agrees not to cause or permit the reverse engineering,
disassembly, copying or decompilation of The Software. The User may
copy The Software only for the purpose of making the permitted number
of installations. In the absence of any written instruction to the
contrary, the permitted number of installations shall be one (1) and
the User may not copy or allow others to copy The Software for any
other purpose. The User agrees not to remove or alter any product
identification, copyright notices, labels or other notices or
proprietary restrictions from The Software or Documentation. The User
agrees not to photocopy or otherwise reproduce any part of the
Documentation or other printed material provided with or in relation
to The Software.
3.2 Information necessary to achieve interoperability of The Software with
other programs within the meaning of section 50B of the Copyright
Designs and Patents act 1988 and the directive of the council of the
European communities on the legal protection of computer programs is
available from JBA.
3.3 As licencee, the User agrees to use its best endeavours to protect The
Software and the Documentation from unauthorised use, reproduction,
distribution or publication and the User agrees to indemnify JBA
against any loss or damage which JBA may incur as a result of failing
to comply with any of the aforesaid conditions.
4. Limited Warranty
4.1 JBA warrant for a period of 90 days from the date that you receive
notice of these terms that the materials of both the product media and
Documentation are not defective and that The Software is properly
recorded on the media. If either the media (such as diskette) or the
Documentation is physically defective, JBA will replace the same
free of charge during the 90 day warranty period. JBA's entire
liability and the Users exclusive remedy for a breach of this limited
warranty shall be the replacement of any defective software or
documentation. To obtain replacement of the software or documentation
in such circumstances please send to JBA:
(i) The name and address of the User
(ii) Your dated proof of purchase (if applicable)
(iii) The disk or other media on which the software is contained
The User must either insure any defective item being returned to JBA
or assume the risk of loss or damage in transit. Please note that
this limited warranty does not cover any material that has been lost,
stolen or damaged by accident, misuse or unauthorised modification.
In no event will the liability of JBA for any damages to the User or
any third party exceed the fee (if any) paid for the use of the
software. Nothing contained herein affects or is intended to affect
the statutory rights of a consumer who purchases the software and the
documentation otherwise in the course of a business.
4.2 JBA warrants that it has the right to licence The Software and the
documentation and JBA will defend any claim that the licensed use of
the same infringes any patent or copyright, providing JBA is promptly
notified in writing of such a claim and JBA is given sole control for
the defence thereof and all related settlement negotiations relating
thereto. JBA accept no liability for a patent or copyright claim
arising from or based upon the alteration or modification of The
Software and the documentation.
4.3 Other than as specifically stated above,
JBA MAKES NO WARRANTY OR REPRESENTATION EITHER EXPRESSED OR IMPLIED
AND SPECIFICALLY DENIES ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR
A PARTICULAR PURPOSE WITH RESPECT TO The Software AND Documentation.
JBA does not warrant that there are no discrepancies between The
Software and Documentation, nor that errors cannot arise during the
use of The Software.
4.4 No JBA employee, Associate, affiliate or agent is authorised to make
any modification or addition to this warranty.
5. Limitation of Liability
IN NO EVENT SHALL JBA (SAVE IN RESPECT OF DEATH OR PERSONAL INJURY ARISING
OUT OF ITS NEGLIGENCE) BE LIABLE FOR ANY DAMAGES HOWSOEVER ARISING,
INCLUDING BUT NOT LIMITED TO ECONOMIC COSTS, LOSS OF REVENUE OR PROFITS,
INDIRECT COSTS, CONSEQUENTIAL LOSS, GOODWILL OR RELATED DAMAGES.
6. General
This agreement shall be governed by the laws of England and is subject to
the jurisdiction of the English courts. The User has read this agreement,
understands it, and agrees to be bound by its terms.
INSTALLATION
────────────
If you are installing Guidelines from floppy disks, please
View Install.Inf
on the first disk.
If you are installing Guidelines from an IBM AS/400, the installation
instructions are contained in an on-line document. To view the document
enter the following command from your PC:
VIEW I:\GUI_INST.ALL\INSTALL.INF
where I: is your PC Support shared folder drive
Icons and Bitmaps
─────────────────
Once Guidelines has been installed, you can extract the icons and bitmaps
(.ICO and .BMP files) by selecting the "Install Images" icon in the
Guidelines folder. If you wish to extract icons for Microsoft Windows
development, select the "Install Windows Images" icon - this will extract
icons which have the extension .ICW and bitmaps which have the extension
.BMW.
There are over 400 icon and bitmap files in each archive.
The Windows Icons are shipped as part of the Windows Code Enable pack.
RUNNING GUIDELINES
──────────────────
After a successful installation you may invoke Guidelines by typing "Guide"
and depressing the Enter key at a command prompt, or via the work place
object created (optionally) during the install.
SYSTEM REQUIREMENTS
───────────────────
The Guidelines Editor requires that you have OS/2 Version 2.1 or
higher already installed on your computer. For information about setting
up OS/2 on your computer, see the instructions in your OS/2 package.
The minimum hardware requirements for running Guidelines are the same
as for OS/2 itself. However the recommended configuration
for Guidelines development is as follows:
■ 486 DX 33Mhz PC
■ SVGA display card and the appropriate monitor
■ 16MB of memory
■ 210MB of disk
Guidelines assumes that you have a supported C++ compiler and the OS/2
Toolkit installed on your hard drive. While applications can be designed
without a C++ compiler, the source code generated cannot be compiled
into an executable unless one is present.
SUPPORTED COMPILERS
───────────────────
Previous versions of Guidelines Desktop provided support for the following
compilers:-
IBM C++ 2.01
Borland C++ 1.00
Watcom C++ 9.5
Borland C++ 3.1
Borland C++ 4.0
Guidelines Version 3.1A is the last release that will support Borland C++
3.1 and Watcom 9.5.
Partial support for Watcom C++ 10.0 is provided with this release, full
support may be released in version 3.2 of Guidelines.
Note: If you migrate from one compiler to another you may need to
regenerate your Guidelines source code to account for variances between
compilers.
RUNNING UNDER OS/2 WARP
───────────────────────
In order for Guidelines to run programs generated with one of the Windows
compilers under OS/2 Warp, the default WinOS2 settings must be changed.
Running Windows sessions under OS/2 2.1 does not require this modification.
Under non-fullpack Warp, a SYS3175 error will occur if a Windows program
is run when the Guidelines default setting of Seamless Sessions is in
place; and the Win-OS2 settings are set neither to fastload or seperate
session. To correct this, and allow Windows programs to be run on the Warp
desktop, your Warp settings should be changed as follows:
Press the right mouse button on the desktop to bring up the main menu and
choose the 'System Setup' option. Activate the 'Win-OS/2 Setup' icon to
access the Settings notebook, and make sure the 'Fastload' or 'Separate
session' options are off, and the 'Win-OS/2 Window' option is on.
If fast load is switched off, the Win-Os/2 session must then be
'initialised' by running a non-Guidelines Windows application
(e.g. the Windows Clock). Guidelines generated Windows programs will
then run on the desktop under Warp.
RUNNING UNDER WINDOWS
─────────────────────
Development considerations
──────────────────────────
The manual 'Guidelines Programming for Microsoft Windows 3.1'
describes the major differences between programming for OS/2 and Windows 3.1.
Help text
─────────
Guidelines will generate a HPJ (Help Project File) and a RTF (the
equivalent of an .IPF file). The Help compiler uses both of these
files to create the .HLP file. Partial IPF tag interpretation is
performed. As the IPF tags are not fully parsed (they are merely scanned
for keywords) any errors in the IPF code will more than likely generate
invalid RTF code.
The following tags are supported when Help text is compiled for Windows:-
Paragraphs :p
Hilited Phrases :hpn
Hyper-links :link (supports reftype hd (header) and fn (footnote))
Multiple fonts :font
Multiple Colors :color
Margins :lm (left margin) and rm: (right margin)
Bitmaps :artwork (linkfile/fit is ignored, center is runin)
Other tags .br (break) :xmp (all other tags are ignored
Running a generated application
───────────────────────────────
To run a Guidelines generated application on a true Windows
machine you should perform the following steps:-
1. Create a new directory on the Windows machine to contain the Guidelines
runtime files:-
MD C:\GUIDE (where C: is your hard disk drive )
2. The following runtime files should be copied from C:\GUIDE\SYS on the
OS/2 machine to directory C:\GUIDE on the Windows machine :-
GCWB121A.DLL G21AWB1D.DLL FCL*.DLL
GCWB221A.DLL G21AWB2D.DLL JPRIKWBD.DLL
GCWW221A.DLL G21AWW2D.DLL
3. The following directory and subdirectories should be created on the Windows
machine to contain your CSS Data:-
C:\CSS
C:\CSS\INC
C:\CSS\WIN
C:\CSS\WIN\BIN
C:\CSS\WIN\DLL
C:\CSS\WIN\HELP
The files contained in these directories on the OS/2 machine should then be
copied to the corresponding directories on the Windows machine.
4. The following files in directory C:\CSS\DATA need to be copied to the same
directory on the Windows machine :
GETCHRID.CLP FILESYN.DAT HOSTAPPL.DAT
HOSTLINK.DAT APPLICAT.INI LOCATION.DAT
USERHOST.DAT JBAGTAB.DAT CODEPAGE.DAT
5. The CONFIG.SYS file must contain the following line:
INSTALL=C:\DOS\SHARE.EXE
6. The following should be added to the PATH in the AUTOEXEC.BAT:
C:\CSS\WIN\DLL;C:\CSS\WIN\BIN;C:\GUIDE
7. The following lines should also be added to the AUTOEXEC.BAT file:
SET CSSUSER=xxxxxxxxxx
where xxxxxxxxxx is the User profile defined as being the local logon Userid
within CSS configuration (see below).
SET JBAFILES=C:\CSS\DATA
SET JBAPASSWRD=C:\CSS\DATA
SET CSSXLAT=C:\CSS\DATA\JBAGTAB.DAT
SET CSSSYN=C:\CSS\DATA\FILESYN.DAT
SET CSSLOC=C:\CSS\DATA\LOCATION.DAT
8. A program group needs to be defined within Windows to allow CSS to be run.
Create a new program group and within it define three new program items
for the following :-
C:\CSS\WIN\BIN\JCFW0000.EXE - define as CSS Configuration
C:\CSS\WIN\BIN\JCHW0000.EXE - define as Maintain Host Applications
C:\CSS\WIN\BIN\JCBW0000.EXE - define as CSS Backup/Restore
C:\CSS\WIN\BIN\JCUW0000.EXE - maintain CSS Users
CSS Configuration can now be run to maintain the local logon Userid
(xxxxxxxxxx).
Once these changes are made, the machine should be rebooted.
You may now run your application.
Notes for this release of Guidelines 3.1 (Tape Gui31d)
──────────────────────────────────────────────────────
INSTALLER
─────────
Please View Install.Inf before installing.
Help is missing from some parts of the Installer.
GUIDELINES PRODUCTS
───────────────────
API 3.10a Design Time Extension Library
APP 1.03a Application Information Extension
BBR 1.33a Button Bar Control
Cannot add a container control to button bar at designtime,
compilation fails with duplicate case error.
Will compile if duplicate REALLOC removed.
Font on buttonbar might not change if the button bar is set to no
border, no auto arrange.
May need to add code in repaints for the button bar.
Multiple default buttons on button bars are possible under Windows.
COL 1.22a Colour Wheel Control
The color wheel will not compile for Windows with Borland 4.0 unless
\Guide\Sys\gColWb2s.Lib is copied to \Guide\Sys\gColWb3s.Lib
Mousepointer may not change over the colorwheel.
The cross hairs on the colorwheel may not behave exactly as expected
but color choice is fine.
Background may not change.
CUA 1.48a Common User Access 91 Controls
Containers
The container method RefreshRecords with a third parameter set to
Cma constants may cause program to crash in Borland4 only.
Notebooks
Dialogs on notebooks MUST be loaded to NullWindow before being inserted
to the Notebook.
Mousepointer on notebook is only honoured over the notebook itself,
not the child dialogs or the PgUp/PgDn Buttons.
Spin Buttons
Small Spin buttons may be invisible in Hi-Res Windows 3.1
Background may not change under Warp.
The minimum and maximum properties need to be set in the
correct order. See the help text.
ValueSets
GetCellAttribute for ValueSets may not always work under Windows.
Slider
problems with repainting in OS/2 especially if the spacing property
is used to larger than design time slider window.
ScaleSpacing property not working properly in Windows Borland 4.0
DBG 1.00d Debugger
Contrary to the help text, the debugger works on Windows with the
Borland 3.1 and 4.0 compilers.
Clicking the 'About..' menu option while stepping through code
can lead to an access violation.
In OS/2 DLL names are not displayed in module listbox.
In OS/2 if a DLL is compiled with debugging turned on and the
program which calls it is not then the User will not have the option to
output information to a file. To do this set debugging to 'none' when
generating the main program.
If the Borland 1.0 OS/2 compiler is used, an access violation
occurs at runtime if the Debug Window is closed during or after stepping
through code.
Windows programs may exceed the 64K memory limit when
compiled with debugging enabled.
If a Windows program calls more than one Guidelines generated
DLL , the DLLs cannot be debugged as the program will not run if any of
the DLLs are generated with debugging switched on.
The '&'s on line 76/column 113, line 80/column 113 and line 82/
column 107 of 'Guidbgw.h' should be deleted.
On entering a switch statement,an if statement or a loop the
Debugger displays an incorrect line of execution.
When using the Debugger with the Borland 1.0 OS/2 compiler the
code has to be generated to use DLLs (Application Settings).
DDE 1.17a Dynamic Data Exchange
DLG 1.26a Standard Dialog Extension
EG1 3.10b Guidelines Samples
FCL 1.07a Windows Support Library
FIO 1.27a File Input/Output Extension
Fileio External Attribute functions will not compile for Windows.
FMT 1.06a Extended Entry Field Formatting Library
GAU 1.21a Gauge Control
GBP 3.10o Guidelines Base Pack
YieldThread does not work for Windows.
For Windows with Watcom 10, there must be at least one control per
dialog. Dll generation is not yet supported.
When resizing listboxes, reset the position
as they have a tendency to move when you change the height property.
Statics Group Boxes
May need to code in repaints
Entryfields
Readonly property not supported. (Borland 3.1)
It is not possible to set the Checked property of a CheckBox via a
copy of the CheckBox in a Window variable.
If many (non modal) frames are processed together, the process for
the first frame may not return until the last frame is dismissed.
The error message "Expecting type 'MODULE' - found 'MODULE'" may
indicate a mismatch between a JOT code module and a JOT thread.
The font details (at run time) may not restrict the font size
according to what is available for the selected font style.
AutoTab property in ComboBox's is not supported.
It is not possible to specify stack or heap sizes > 99999 bytes.
(Note that in Windows, both must be < 64K, 24K is sensible).
Help message invoked from a thread may not be displayed.
GLU 1.08a Guidelines Utilities
GRA 1.00a Graph Control
Duplicate hot key for control in create menu, Gauge is default
for 'g' hot key.
Do not set the .XAxisText and .YAxisText properties to strings
whose length is greater than 30 characters.
The graph control only allows values up to 32767.
SetFont will have no effect on a Graph control.
The quatity of text displayed at any time is proportional to
the size of the graph.
GRD 2.08a Grid Control
The CharSet property should not be used for OS/2 or Windows as it causes
a crash whenever assigned to a cell.
The Scrollbars do not fully correspond to the displayed cells, you
should make no assumptions about which cells are displayed from the
position of the scrollbars. Under OS/2 the vertical scrollbar's
position isn't perfectly aligned with the edge of the grid window.
Changing the Presentation Parameters will result in a strip of colour
down the side.
It is possible to cause list boxes to be created with incorrect
widths by setting the list flag for a cell that is not visible
in the Grid window.
The SetGridColWidth method is not totally reliable; it is best to set
the width of a column using the ColWidth property.
Under Windows, HideColumn can blank a grid when several columns are
hidden and subsequently refuse all entry to cells. Under both OS/2 and
Windows, HideColumn can affect the display of the grid if a column that
is not visible in the Grid window is hidden.
Under Windows, navigating the grid using the cursor keys will not
respond correctly to ReadOnly cells, the cursor will skip over any
readonly cells but also skip over the adjacent cell to these.
The grids GainFocus event has problems under Watcom 9.5 (OS/2).
Repeatedly changing focus from cell to cell will cause a crash,
as such using a grid control under this compiler is not recommended.
ICN 3.10b OS/2 Images
Guide.Icw is in this self extracting archive.
ICW 3.10c Windows Images
Guide.Icw is not in this self extracting archive.
JPR 1.00b Basic Print Support
Only one page can be printed at a time.
LED 1.00a LED Control
Duplicate hot key for control in create menu, List
box is default for 'l' hot key.
Top, Right alignment setting may cause invisible text.
PDK 3.10r Professional Developer Kit
This is the version of the 01PdkPck pack
PIC 1.40a Picture Panel Control
Toggle ,Multistate & SetPicture button can if clicked lightly
mousepointer, change the image, without the .state property
actually changing or the click event being activated. Pictures
may not be displayed on Picture Panels in Windows.
Tabbing from some styles of picture button causes lost focus.
Focus can however be regained by mouse click.
PRO 1.13a Profile Maintenance
SMU 1.08a Softmenu Control
Duplicate hot key for control in create menu, Static is
default for 's' hot key.
Smu icon is database icon on low res (VGA) machines.
When a SMU menu changes vertical height (wrapping from one line
to two, two lines to one, displaying a bitmap etc), it does not
change the vertical height of the frame it is on. Hence something
must happen to the difference in space between what it did
occupy and what it occupies now. Under OS/2, every control
stays fixed, hence any controls directly beneath the menu may
get obscured, but still received mouse clicks. Under Windows,
everything is moved by the change in height, so controls near
the bottom may get pushed below the edge of the frame.
The sample SoftMenu files have hardcoded file names. These
hardcoded names point to the absolute path of softmenu files to
be loaded, and should be changed to point to the location of
the softmenu files on your machine.
SOM 0.70a System Object Model Extension
STA 1.36a Status Bar Control
Duplicate hot key for control in create menu,
Static is default for 's' hot key.
SYI 1.03a System Information Extension
TBR 1.30a Toolbar Control
Font on toolbars must be set for specific controls, Not the
whole toolbar.
TFX 1.11a Enhanced Text Control
The ReflDir() & StretchDir() with parameters TfxHorizontal, TfxVertical
and TfxBoth Will NOT compile for any platform.
The Help text describes .Alignment property - this property has been
replaced by the .textAlignment property.
The ShadowAngle property & the SetEffect(Hollow) method have no
effect in Borland4.
The enhanced text wordwrap property does not work as expected.
TIM 1.24a Timer Control
Your Operating system seperator defaults might not be honoured
by the Guidelines timer functions.
TMF 1.06a Timer Function Libraries
W31 3.10l Windows Code Enable Pack
This is the version of the 16W31Pck pack
Possible Multiple default icons in Windows.
There may be difficulty in passing Images between functions in Windows.
Message boxes moveable property may be inconsistent between OS/2
and Windows.
XEF 2.23a Extended Entry Field Control
The NullAllowed function is not currently supported.
You cannot use both the Extended Entry Field and the repository control
in the same application.
XEL 1.05a Formatting Functions
WARP
Programs compiled for Windows with the Run In Seamless Windows option
set, should be run from a command line, not from the Guidelines
Main Frame.
There may be some paint problems when there are many controls
on one dialog.
Static text may default to be displayed with a white background.
HELP
The following help may not be supported in the Guidelines editor.
o Main Menu, Edit, Resources, Check
o Button, Image(Type), Resource screen
o MainMenu, Output, Options has no help for Debug.
o Extended Entry Prompter for properties.
CLIENT SERVER PRODUCTS
──────────────────────
ASU 1.01a Guidelines AS/400 Client/Server Utilities
CS2 3.10u Client/Server Support
This is the version of the 03Cs2Pck pack
CS4 3.10p Guidelines Client/Server AS/400
This is the version of the 04Cs4Pck pack
CSP 0.77i Low Level Client/Server
Please see the ReadMeFirst section in the Low Level CSS help text.
Positioning file pointers to the beginning or end of a file based
on a non existent key may cause problems.
Reading records locked from a DB2 view may cause problems.
SetFilePointerAfter may only place the file pointer after the first
of a number of duplicate records. A similar problem may exist with
SetFilePointerBefore.
CSS 1.11a High Level Client/Server
There may be problems under Windows when two Exes connect to an
AS/400. The root of this problem may be with Csp, Syn, Lck or Gbp.
In the CSS Configuration utility, the default buttons remains
whatever is pressed first after entering program.
DBC 3.10n Database Connectivity
This is the version of the 02DbcPck pack
GDB 2.27a Repository Control
You cannot use both the Extended Entry Field and the repository control
in the same application.
Notification messages from the the repository control can sometimes
get pushed back to be obscured behind the Guidelines main window.
In particular, during startup, a notification of missing-or-changed
repositories is often pushed back when the flash screen is displayed.
GDW 2.05e Guidelines Development Workframe
The following problems are still to be addressed:
o Repaint after Maximise, Restore can be erratic. Using Windows menu
Tile or Cascade, can restore field or files lists.
o When creating a new Project, changing an AS/400 library is not
reflected in the AS/400 Object creation frame. File is updated
correctly.
o Pressing OK Button on Project maintenance appears not to work.
However, this is due to an incorrect path being specified, for which
no error box is displayed.
o Container split bar position incorrect in some resolutions.
o If relative paths are entered in Project maintenance, attempting
to create them will result in paths being built in install
directory. If empty path is entered on page 2, program fails: use
"*NONE".
o Editing of Constraints in Maintain Table or View is incomplete.
o Maintenance of Joined file definitions, validation is incomplete.
o Substring/Concat facilities unsupported.
o Import AS/400 Definitions does not support Join files. They are
currently treated as Logical Views. This should provide sufficient
information for use with Database control, but NOT to re-create
the file.
o Use of keyboard on AS/400 Import window is inconsistent. Keys other
than the button short cuts (Help, Refresh etc.) cause the file list
to scroll to a line starting with the letter pressed.
o Focus can be given to a previous frame when intended to be modal.
This can only be done once, and is not always posible. Under
investigation.
o DB/2 Target does not support Constraints, Unique key or Join files.
GWF 1.05a Guidelines Workframe
This is the RPG server logic extension. Problems can be experienced
loading Gwf.Gue when Guidelines starts up if IBMs PC Support is
not running. If you do not want to use this extension and have
already installed it, when Guidelines is not running,
Rename \Css\Os2\Gue\Gwf.Gue to \Css\Os2\Gue\Gwf.Gu
o Variable-names of greater than 6 characters will cause problems
in generated RPG.
o When using the STR() function, variable names less than 3
characters long will cause the compile to fail.
E.g. STR(rc) will fail, but STR(retc) will be okay.
o Parameters may be passed only to the Mainl() function when coding
the Guidelines JOT modules. The parameter must be a structure,
and only one may be specified.
o Mainl() MUST be coded first in time; the RPG generator is expecting
Mainl() to be the first module found in the resulting code. If
Mainl() is deleted and then re-coded (when other modules are
present), then the RPG generation will fail.
o The arithmetic functions + and - (add and subtract) will
occasionally cause memory allocation problems. To get around
the problem when it occurs, close down Guidelines and Guidelines
Development Workframe, and then re-open them, and continue.
o The JOT switch statement is not catered for in the RPG generator.
o Array handling not supported.
o Calling programs with the RunProgram() function results in a number
of problems: (1) RunProgram() MUST be given a parameter and it must
be a string. (2) If formatted data is being passed, and the TOSTR()
function is used to convert a structure to a string, the RPG
generation will fail.
o After generating RPG from JOT, changing to another project and
attempting to generate (C++) may result in a compilation failure.
This is under investigation and may be due to memory allocation
problems. To get around the problem, close down Guidelines and
then restart.
JCF 1.01b Client/Server Configuration
When configuring under Windows, there can be problems if the
dialogs for maintaining Hosts, Databases or Directories are
closed and opened again.
JIX 2.16b Local Index File Support
A number of enhancement requests are under consideration.
JMC 1.01c Message Layer Configuration
Please see the ReadMeFirst and Enhancements/Known Problems sections
in the Msg help text.
JNP 0.01a Named Pipe Support
JUT 1.04a Configuration Framework
LCK 1.00e Memory Locking Layer
LDA 0.76l Local Data Area
The LDA is used by Guidelines Development Workframe and so
should not be used whilst GDW is running.
MSG 0.83i Message Layer Support
Please see the ReadMeFirst and Enhancements/Known Problems
and MsgSaveWindow sections in the Msg help text.
There are some problems using the Debugger with the Msg Layer.
Tracing through functions in Dlls that were loader by the Msg
Layer may show the incorrect function names. Exiting the
debugger may also cause problems (not sure where the root
of the problem is). Note that the Msg layer has its own trace
functions.
"*new" in error messages refers to the Constructor.
"*del" in error messages refers to the Destructor.
NLS 2.20a Guidelines National Language Support
PCS 2.21a Guidelines PC Support Extension
A crash with the message
EHNDQAPI->EHNCM00.ACTIVECONVERSATION
indicates an old version of IBMs PC Support.
QEL 1.16a Guidelines Q+E Database Functions Extension
RSQ 1.00b Guidelines Remote SQL Server Support
AS/400 SQL Support.
Signed Numeric fields with Negative values are not translated correctly
when bound (SQLBindReal(), SQLBindLong()) to JOT real or long
variables. This does not affect values retrieved by the
SQLGet<datatype>Column() functions. (OS/2 and Windows).
Note. Calling SQLExec() to create SQL objects (Table, View, Index,etc.)
into a Library rather than a SQL Collection always returns -1021
(SQLExec() failed), when in fact the object is created.(OS/2 and
Windows).
DB2/2 SQL Support.
SQL String type (CHAR, VARCHAR, etc.,) column values may be
returned that are not null terminated, i.e. extra characters
appear in the associated JOT string variable (see
SQLBindString(), SQLGetColumn and SQLGetStringColumn). By using the
SQLColumnInfo() function or the DB2/2 SQL LENGTH function the actual
length of the value can be determined. (OS/2).
Null values are not supported by the SQL extension for DB2 or AS/400.
SYN 1.34b Synonym Layer
A significant update has been made to the Synonym layer (used
by CSS). The previous versions of the Dlls have been shipped
with extensions .Dl for reference.
GENERAL ISSUES
──────────────
The character translation table editor EdtGTab is only available
under OS/2.
Client Server functions do not support files with field options
"O" = Open, "J" = DBCS and "E" = SBCD or DBCS.
If a structure is supplied by a GUE (e.g. a repository item), any char array
members are not initialised to blanks.
The only supported CSS compilers are
IBM C set ++ for OS/2 and Borland 4.0 for Windows.
GUIDELINES SUPPORT
──────────────────
For assistance in locating your nearest Support Centre, please
telephone one of the International numbers listed below:
AFRICA (Johannesburg, South Africa) +27 11 804 5062
ASIA PACIFIC (Sydney, Australia) +61 2 748 7822
EUROPE (Birmingham, UK) +44 (0)1527 550 558
AMERICAS (Chicago, USA) 708 590 0299
TRADEMARKS
──────────
* IBM, C Set++, Operating System/2, OS/2 and Presentation Manager are
trademarks or registered trademarks of International Business
Machines Corporation.
* Windows is a registered trademark of Microsoft Inc.
* Borland C++ is a trademark of Borland International Inc.
* Watcom C++ is a trademark of Watcom International Corporation