HP3000-L Archives

April 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gary Sielaff <[log in to unmask]>
Reply To:
Gary Sielaff <[log in to unmask]>
Date:
Tue, 18 Apr 2000 11:19:07 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (124 lines)
What can I say... I was (evidently) wrong..  BBUUUUUTTTTT... I think there
is a whole lot a shakin(CM) goin on.
I'll just but out and go quietly..... snivvel snivvel
Busted in Moses Lake
Gary

----- Original Message -----
From: <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, April 18, 2000 10:35 AM
Subject: Réf.[2]: QTP as a system hog


> John Pickering wrote :
> >>Try again Gary!
> >>ACCOUNT=  COGNOS      GROUP=  PH819C2
> >>FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
> >>                 SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX
> >>QTP       NMPRG   128W  FB        8393       8393   1     8400  1  8
>
>
> The QTP program file certainly is an NMPRG file,
> but there are CM things going on in there which are
> beyond the ken of mere mortals !
>
> We recently had the following abort from a QTP program ...
> Would anyone have any explanations for this ?
>
> Executing request CREATE-FILE ...
>
> **** COMPATABILITY STACK OVERFLOW
> ABORT: QTP.PH729C8.COGNOS
> Error capturing state - CM mode - Translated
> NM address does NOT map back to trans CM code.
> Translated code may be executing CM millicode.
> CM address is unknown.  GHOST2 seg 1.13 used.
> Special CM stack marker cap.  CM was interrupted
> Cap has been removed.  ISM used to get CM state.
> NM SYS   a.0022bbb4 $$lr_wa_30_long+$4
> NM PROG  2058.00103f24 qSortRetrieve+$150
>
> RUN QTP.PH729C8.COGNOS;INFO="AUTO=MCYW52PP.LNP1 ";XL=" *PHLIBXL"
> Program terminated in an error state. (CIERR 976)
>
>
>
> From:     [log in to unmask] on 18/04/2000 16:57 GMT
>
>
> Try again Gary!
>
> ACCOUNT=  COGNOS      GROUP=  PH819C2
>
> FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
>                   SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX
>
> QTP       NMPRG   128W  FB        8393       8393   1     8400  1  8
>
>
> > -----Original Message-----
> > From: Gary Sielaff [SMTP:[log in to unmask]]
> > Sent: Tuesday, April 18, 2000 1:03 PM
> > To:   [log in to unmask]
> > Subject:      Re: QTP as a system hog
> >
> > That's because QTP is in Compatability Mode instead of Native Mode.
> > Cognos
> > never converted it and the last time I talk to the Techy folks they said
> > it
> > would not be converted.  Sorta reminds me of FCOPY.
> > Powered out in Moses Lake
> > Gary
> > ----- Original Message -----
> > From: Dave Knispel <[log in to unmask]>
> > To: <[log in to unmask]>
> > Sent: Tuesday, April 18, 2000 9:39 AM
> > Subject: QTP as a system hog
> >
> >
> > > To all,
> > >
> > > I'm working on an HP3000 using QTP version 8.19.C2.  I have a QTP
> > process
> > > that is reading a NM/KSAM file, doing a select, sorting, then writing
> > out
> > > two subfiles.  This process keeps taking over my system.  Even running
> > in
> > > the EQ it will take all available system resources so no one (even the
> > folks
> > > in a higher queue) can get any CPU time.
> > >
> > > Has anyone seen this before?  Any help would be appreciated.
> > >
> > > I'm posting this to both the HP3000-L and the Powerhouse-L.
> > >
> > > David Knispel
> > > [log in to unmask]
> > > Phone: 513-248-5029
> > > Fax: 513-248-2672
>
>
>
>
>
> --------------------------------------------------------------------------
--------------------
> This message is confidential; its contents do not constitute a
> commitment by BNP Paribas Group* except where provided
> for in a written agreement between you and BNP Paribas Group*.
> Any unauthorised disclosure, use or dissemination, either
> whole or partial, is prohibited. If you are not the intended
> recipient of the message, please notify the sender immediately.
> *BNP Paribas Group  is a trading name of BNP SA and Paribas SA
>
> Ce message est confidentiel; son contenu ne represente en
> aucun cas un engagement de la part du groupe BNP Paribas*
> sous reserve de tout accord conclu par ecrit entre vous et le
> groupe BNP Paribas*. Toute publication, utilisation ou diffusion,
> meme partielle, doit etre autorisee prealablement. Si vous n'etes
> pas destinataire de ce message, merci d'en avertir immediatement
> l'expediteur.
> *Le groupe BNP Paribas est le nom commercial utilise par BNP SA et Paribas
SA

ATOM RSS1 RSS2