|
You are aware that you have "#bookmark" in the interactive string andthe
"#bmark" in the CLP, right? I'd expect it to position to the top if
there is not matching bookmark in the document.
- --
Pete Hall
pete@xxxxxxxxxxxxxx
On 2010-11-19 17:18, Karl Abbott wrote:
I want to put the help text for my application into an HTML page and
store it on the IFS.
The HTML will contain anchor tags (bookmarks) that allow positioning
stripsuser at the appropriate section of the help text.
If I go into a browser and type
file:\\iseries\root\folder\helptext.html#bookmark
<file:///\\iseries\root\folder\helptext.html#bookmark> it works
perfectly.
But when I put this into a CL program using the following code it
page.off the #bmark, which means it always positions to the top of the
PGM
DCL VAR(&CMD) TYPE(*CHAR) LEN(98)
DCL VAR(&path) TYPE(*CHAR) LEN(50)
STRPCO PCTA(*NO)
monmsg cpf0000
chgvar var(&path)
value('file:\\iseries\root\folder\helptext.html#bmark')
chgvar var(&cmd) value('rundll32 url.dll,FileProtocolHandler ' *bcat
&path)
STRPCCMD PCCMD(&cmd) pause(*no)
ENDPGM
Any suggestions?
Thanks, Karl
I want to put the help text for my application into an HTML page andthe
store it on the IFS.
The HTML will contain anchor tags (bookmarks) that allow positioning
user at the appropriate section of the help text.strips
If I go into a browser and type
file:\\iseries\root\folder\helptext.html#bookmark
<file:///\\iseries\root\folder\helptext.html#bookmark> it works
perfectly.
But when I put this into a CL program using the following code it
off the #bmark, which means it always positions to the top of thepage.
PGM
DCL VAR(&CMD) TYPE(*CHAR) LEN(98)
DCL VAR(&path) TYPE(*CHAR) LEN(50)
STRPCO PCTA(*NO)
monmsg cpf0000
chgvar var(&path)
value('file:\\iseries\root\folder\helptext.html#bmark')
chgvar var(&cmd) value('rundll32 url.dll,FileProtocolHandler ' *bcat
&path)
STRPCCMD PCCMD(&cmd) pause(*no)
ENDPGM
Any suggestions?
Thanks, Karl
On 11/20/10 7:23 AM, dieter.bender@xxxxxxxxxxxx wrote:constraints
... seems to be pure marketing to me, I didn't find any
documentation, how it works and about measurable benefits...
Birgitta Hauser wrote on Saturday, November 20, 2010 3:24 PM:
What about "constraint awareness", a technology that checks
constraints and handles them in a special way?
Check constraint awareness and RI awareness were both introduced
within the SQE in Release V5R3M0.
The DB2 SQL for i [the SQE] does utilize information from
for making some decisions. There had even been a defect, early-on,having
whereby an error in implementation effected incorrect output for
omitted rows for values which were actually in the database.access
For example, the database can implicitly know that a value that is
not in the parent will not be in the child, and can optimize the
plan and path for data retrieval with that understanding. Thatspecific
utilization of constraint awareness was the source of theaforementioned
defect, though I do not recall the details [perhaps applying rulesfrom
a constraint that was not enforced per CHGPFCST STATE(*DISABLED) or ina
CHECK PENDING status]. Similarly, logic in a check constraint can
eliminate selection rules, probes, and actual retrieval of data that
"can not exist" according to the rules. Note that such logic makes
little sense with regard to the TABLE [on which the constraints are
defined] for the latter two, since the physical data is just not there
[else there is a highly negative defect]; the logic applied from
constraints definitely assists for improvements on [implementations
effected as or similar to] join logic. If you have many values 'X' in
column used to join on a column in a child file whose parent has noif
value 'X', then there is no need to inquire of any INDEX on the child
there are any rows with the value 'X'; i.e. there must not be any
'X'-rows in the child, thus do not perform any actions that might
otherwise lead down the path to locate any such rows.
--
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.