Stuck with security in Axiant (Was: Re: Can't find explanation for warning msg in QUICK)
Michel Adam
michel.adam at gmail.com
Mon Jan 18 18:08:47 CST 2010
Thanks to Ken, I was able to make some progress. However, I am now stuck on
the 'Build' (or lack of...).
I was able to create the files, (looks like a 'direct' file has to be
created manually?) . Now the issue is, how to 'BUILD' the screens? I have
migrated/imported the screens, but the 'build' function, once I have
imported the source screens, is obstinately grayed out (The 'F7' function).
I think I missed a crucial step (or two). Looking at the documentation, I
can't see anything obvious. Any ideas what it might be?
Michel
On Mon, Jan 18, 2010 at 10:08 AM, Michel Adam <michel.adam at gmail.com> wrote:
> Trying to dust-off/revive a proof-of-concept project, I get errors with
> Axiant when migrating a prototype application from MPE to Windows:
>
> All the files/records are KSAMXL (with one DIRECT/FLAT MPE file), and I am
> tripping over security when trying to create the files. Typical message is:
>
> >
> >
> >
> > ;Generating Files for the File Collections
> > ;rodfiles
> >
> > CREATE FILE PLCITEMS
> *W* Some files have not been processed due to insufficient security.
> The original PHD source has this:
>
> ;
> ; -------------------------------------------- Globals
> ; Created on Fri Jan 15 19:51:18 2010 by utility program
> ;
> Create Dictionary RODPHD &
> Not Preloaded
> System Options &
> Title "Records Of Decisions" &
> Century INCLUDED &
> Character Set ENGLISH &
> Date Format YYYYMMDD &
> Date Separator "-" &
> Default Century 20 &
> Allow Century &
> Force Century &
> Input Century 19 From Year 50 &
> NoNullseparator &
> Float IEEE &
> Sysmonths "JanFebMarAprMayJunJulAugSepOctNovDec" &
> SHOW &
> Default Entry and Find in CONSISTENCY &
> Default Select in CONCURRENCY &
> Default Transaction Model CONCURRENCY &
> Shift UPSHIFT
> Application Security Class GOD &
> Logonid MIA0.ADOPTDEV
>
>
> [...]
>
> File PLCItems Organization INDEXED &
> Type KSAMXL &
> Open "PLCItem" &
> Create ASCII &
> Capacity 1000
>
> Record PLCItems
> Item ItemKey &
> Datatype INTEGER Unsigned Size 4
> Item ItemType &
> Datatype CHARACTER Size 1
> Item ItemTitle &
> Datatype CHARACTER Size 100
> Item AssignedTo1 &
> Datatype CHARACTER Size 8
> Item AssignedTo2 &
> Datatype CHARACTER Size 8
> Item AssignedTo3 &
> Datatype CHARACTER Size 8
> Item AssignedTo4 &
> Datatype CHARACTER Size 8
> Item ItemComments &
> Datatype CHARACTER Size 100
> Item ItemOriginator &
> Datatype CHARACTER Size 1
> Item SentDate &
> Datatype INTEGER Unsigned Size 4
> Item SignedDate &
> Datatype INTEGER Unsigned Size 4
> Item ApprovedFMB &
> Datatype CHARACTER Size 1
> Item FMBSubType &
> Datatype CHARACTER Size 4
> Index PLCItemIDX Unique Primary
> Segment ItemKey &
> Datatype INTEGER Unsigned Size 4
>
>
> Trying to keep it simple, what magic incantation should I use to migrate a
> bunch of KSAMXL and one DIRECT file from the 3000 to the PC, with the
> minimum fuss? CISAM, DISAM ? Any gotchas I can avoid by changing the
> source on the 3000 ?
>
> I was hoping to keep it as simple as possible by not using anything more
> complicated than index files. But even that does not seem likely.
>
> As well, any tricks to have everything compile without hiccups? Maybe
> getting rid of group qualification in file names? merging in the USE files
> in screen source?
>
>
>
> Michel
>
>
>
> On Sat, Jan 16, 2010 at 6:27 PM, Michel Adam <michel.adam at gmail.com>wrote:
>
>> Yep Bob, 819C1, on a 968:
>>
>> :qdesign
>> Q D E S I G N (PowerHouse 8.19.C1)
>> Copyright 1998 COGNOS INCORPORATED
>> GNWT
>> > use rdde07s.source nol
>> Mode:x Action:xxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> xxxxxxxxxx
>> xxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> xxxxx
>>
>> ********************************************************************************
>>
>> 01 Item Key: xxxxxxxxxx
>> 02 Item Type: x
>> 03 Item Title:
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> 04 Assigned To(up to 4):xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
>> 05 Item Comments:
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> 06 Rc'd from Originator x
>> 07 Sent to Minister: xxxxxxxxxx
>> 08 Signed by Minister: xxxxxxxxxx
>> 09 Appr.Accpt.Cab/FMB: x
>> 10 FMB Submission Type: xxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 0 ERRORS 0 WARNINGS. Delete old screen RDDE07C.EXEC.ADOPTDEV?y
>> >
>> from within Quick:
>>
>> Mode:F Action:i Records Of Decisions
>> 2010-01-16
>> RDDE07 Plcitems
>> 16:51
>>
>> ────────────────────────────────────────────────────────────────────────────────
>> 01 Item Key:
>> 02 Item Type:
>> 03 Item
>> Title:
>> 04 Assigned To(up to 4):
>> 05 Item
>> Comments:
>> 06 Rc'd from Originator
>> 07 Sent to Minister:
>> 08 Signed by Minister:
>> 09 Appr.Accpt.Cab/FMB:
>> 10 FMB Submission Type:
>>
>>
>>
>> QUICK819C L4 RDDE07C.EXEC.ADOPTDEV(10-01-16) QDESIGN819C HP700/92 (c)
>> COGNOS
>> INCORPORATED.
>> Press RETURN to continue.
>>
>> That will show me about using the docs of the current version with an
>> older release. I ended up using PH 8.19 to minimize issues with Architect,
>> which is itself at 8.19, but was going by with the current documentation.
>> Since I was not getting any compilation errors...
>>
>> I guess the dynamic list syntax has been in Qdesign for quite some time. I
>> have removed the option on the fields that had it. Problem solved.
>>
>> Thanks for the clarifications Bob.
>>
>> Michel
>> On Sat, Jan 16, 2010 at 3:24 PM, Bob Deskin <Bob.Deskin at ca.ibm.com>wrote:
>>
>>> Dynamic lists were originally in Axiant. They're like selectboxes (i.e.
>>> drop-down lists of values), except that the values come from a file. We
>>> adapted the dynamic list for PowerHouse Web. So even though the
>>> DYNAMICLIST syntax was in QDESIGN and the result was in the compiled
>>> QUICK
>>> screen, QUICK itself did not use it. We did open up the DYNAMICLIST
>>> syntax
>>> for full QUICK in 8.49F.
>>>
>>> Are you sure of your versions? Dynamic lists were added for PH Web in D1.
>>> So the warning would appear if you called a screen that was version D1 or
>>> E that was compiled with a DYNAMICLIST. Of course you'd have to be
>>> running
>>> QUICK D1 or E to get that message.
>>>
>>> Bob
>>>
>>>
>>>
>>> From:
>>> Michel Adam <michel.adam at gmail.com>
>>> To:
>>> power-l <powerh-l at lists.sowder.com>
>>> Date:
>>> 2010-01-15 11:11 PM
>>> Subject:
>>> Can't find explanation for warning msg in QUICK
>>> Sent by:
>>> powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com
>>>
>>>
>>>
>>> Under 819C, I get the following warning when calling a subscreen:
>>>
>>> *w* Screen with dynamic list fields is not supported in Quick.
>>>
>>> I looked at the QKINFO, QKDINFO, and in the fine manual, and no mention
>>> of
>>> this warning.
>>>
>>> What triggers this?
>>>
>>> Stumped North of 60...
>>>
>>> Michel Adam
>>> --
>>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>>> Mailing list: powerh-l at lists.sowder.com
>>> Subscribe: 'subscribe' in message body to
>>> powerh-l-request at lists.sowder.com
>>> Unsubscribe: 'unsubscribe <password>' in message body to
>>> powerh-l-request at lists.sowder.com
>>> http://lists.sowder.com/mailman/listinfo/powerh-l
>>> This list is closed, thus to post to the list you must be a subscriber.
>>> Add 'site:lists.sowder.com powerh-l' to your search terms to search the
>>> list archive at Google.
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20100118/684c92d3/attachment.htm
More information about the powerh-l
mailing list