ca.portal.admin

Issues with MAPC

Discussion created by ca.portal.admin on Feb 18, 2005
When I was modifying the map in MAPC , the region went down and when the
region came up it is not allowing me to view the map using MAPC.
Giving an error

""PREVIOUS TASK ABENDED WITH ABEND CODE D002 AND MESSAGE CODE 245008""
What to do now ?



Could anyone help with a sample JCL to punch out and punch in MAP
to/from TSO ?


Thanks in advance
Babija




Confidentiality Notice


The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Issues with MAPC
"When I was modifying the map in MAPC , the region went down and when the
region came up it is not allowing me to view the map using MAPC.
Giving an error

""PREVIOUS TASK ABENDED WITH ABEND CODE D002 AND MESSAGE CODE 245008""
What to do now ?



Could anyone help with a sample JCL to punch out and punch in MAP
to/from TSO ?


Thanks in advance
Babija




Confidentiality Notice


The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
XOMT/CMMT sorting
"Fellow IDMS-Lers,

Does anyone know if it is possible to sort output screens in CMMT/XOMT?

Sam

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Signon dialog

IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
unsubscribe
"

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Signon dialog
"Robin

I have an Assembler program which identifies whether a user's profile
includes a Clist, and if so calls RHDCCLST to execute it; which, as you
describe, is invoked as an autotask for each online LTERM. Whether it could
be adapted to invoke an ADS dialog, I cannot say. The program as it stands
could be used to cause the execution of a Clist including the command: ADS
'dialog-name'.

However, that is not the end of the matter, because the Assembler program
annuls (necessarily, I was told by CA) the autotask in the LTE, and this
therefore has to be reset when the user signs off; otherwise, the next user
to be assigned that LTERM will not get the autotask invoked. This we do
with a signoff (#2) exit - which in turn entails revising RHDCUXIT to
point at the exit. I can also supply our exit as an example of what is
necessary.

If this is of interest, let me know direct, and I will provide the source
code mentioned. I am curious, however, why your client requires a dialog
rather than relying on the native IDMS capability with Signon internally
secured, that expects a User Id and password to be supplied at the 'Enter
next task code' prompt. I am also curious how the dialog expects to
validate the Id and password entered. If this is against an IDMS database,
it sounds to me like reinventing a wheel that already functions perfectly
satisfactorily from the IDD or external security such as ACF2, depending on
whether Signon is secured internally or externally.These have the
additional benefits of encrypted passwords and, in the latter case, time
expiry of passwords.


Disclosure of Material Facts
Every Proposer or Insured / Reinsured when seeking new insurance / reinsurance or renewing an existing Policy must disclose any information which might influence the Insurer / Reinsurer in deciding whether or not to accept the risk, what the terms should be, or what premiums to charge. Failure to do so may render the insurance / reinsurance voidable from inception and enable the Insurer / Reinsurer to repudiate liability.

This email, together with any attachments, is for the exclusive and confidential use of the addressee(s) and may contain legally privileged information. Any other distribution, use or reproduction without the sender's prior consent is unauthorised and strictly prohibited. If you have received this message in error, please notify the sender by email immediately and delete the message from your computer without making any copies. While attachments are virus checked, Aon Limited does not accept any liability in respect of any virus which is not detected.

Aon Limited
Company Number: 210725
Registered Address: 8 Devonshire Square, London, EC2M 4PL

Aon Limited is authorised and regulated by the Financial Services Authority in respect of insurance mediation activities only

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
an exchange on IBM-MAIN ... (i guess he knew better than to post to idms-l ...)
"On Mon, 2005-02-21 at 15:28 +0530, jayaprakash.muthirevulu@WIPRO.COM
wrote:
Any one help you regarding the detailed approach note on migration from
IDMS database to DB2
I guess the guy from Wipro is doing an IDMS to DB2 conversion and hopes
that a shotgun query to ibm-main will net him a ""detailed approach"".

Ever hear of Wipro? Worth doing a Google search.

Mr. Jayprakash, I have many friends who have lost jobs to people in
India. That's fair; it's what a competitive economy does. Competition
keeps everyone sharp. But you aren't making an effort to be competitive
in anything but price, and are looking for somebody else to do your job
for you.

It's simply not in my best interest to do your job. I would be happy to
help, but not willing to be taken advantage of.

--
David Andrews
A. Duda and Sons, Inc.
dba@duda.com









Chris Hoelscher
IDMS & DB2 Database Administrator
Humana Inc
502-580-2538
choelscher@humana.com





The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
ISPF problem
"Hi Listers:Not an IDMS issue here but I thought I'd ask...

I'm not sure how this occured but I just need to get out of this current problem regarding ISPF.

I executed a clist with today as part of our migration process.

Normally I fill in the panel, hit enter, submits my jcl.

Instead of submitting jcl I got the following:
IKJ56269I DATA SET DPJWD.SPFTEMP2.CNTL NOT FOUND

I had my ISPF profile renamed. Created a new one at signon to tso again.
This time I get:
IKJ56269I DATA SET DPJWD.SPFTEMP1.CNTL NOT FOUND

Does anyone know how to fix this? Thanks everyone.


J. Wayne Doneker
United Defense
York Pa.
717 225 8109
Email: john.doneker@udlp.com

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
SQL constraint violation
"While running the ""create constraint"" utility on already existing
tables, a user's job failed with the following message: ""DB002121
C-4M6004: CONSTRAINT VIOLATION"". However, the utility does not give any
indication of which row has the problem. Is there any easy way to find
the bad key, or any way to get the utility to display it?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
what I learned when converting to release 15.0 ....
"two ""gotchas"" i discovered when upgrading to 15.0 ...

1) in 14.1 - we had a CV where the memory required to fufill buffer
requests exceeded the amount of storage available to us from the opsys
(please don't ask why we needed so much) ...at startup, when we could not
get the storage we needed, the CV allocated what it could and went on its
merry way ...

in 15.0, however, the startup croaked when it could not provide the
buffers with the needed memory. TD67596 was written to address this.


2) we are staging our implementation of LE. when we first converted to
15.0, LE had no role. Then, I sysgenned RHDCLEFE & CEEPIPI, and put LE
libraries in our CDMS LIB concatenation. I brought up the Cv after each
step. It seems that the CV thinks LE is supported (confirmed by DCPROFIL)
if RHDCLEFE is sysgenned - so even when the LE libraries were not yet in
play, the first execution of a COBOL II dc cobol program would attempt to
call CEEPIPI, and, therefore fail. Afterwards, the CV would realize that
LE was not supported, and all would be fine (and DCPROFIL) would correctly
reflect that LE was NOT Supported). Once the LE runtime libraries were in
play - all was fine.


Chris Hoelscher
IDMS & DB2 Database Administrator
Humana Inc
502-580-2538
choelscher@humana.com





The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: what I learned when converting to release 15.0 ....
"We have multiple systems sysgened in the same CV here too. Our shop
migration path is setup as Test, QA (quality assurance), then Prod CV's.
The QA CV's have two systems in then say system 17 and 7. QA comes up as
system version 17 cv number 17, Prod comes up as system version 7 cv
number 7. We use FDR backup/restore to move QA to Prod. Never had a
problem with sysgening this way although I remember some problems way
back when with vtam applid's if the line name wasn't unique to each
system number.

Steve Harmeson

Outcomes