ca.portal.admin

Re:DB Segmentation

Discussion created by ca.portal.admin on Feb 10, 2006
Once again I would like to tap into the vast knowledge pool that is IDMS-L.

We are considering a major modification to an existing IDMS database. Due to the growth of the data within IDMS, we are considering splitting this database into several smaller entities. Example: all customers whose accounts start with ""1"" go into DB1, accounts that start with ""2"" go into DB2, etc. Some mechanism would be used (system exit or
programmatically) to determine which database is accessed and stored.

Are there any other IDMS shops out there doing something like this? Would you be willing to discuss this topic with me and let us know the benefits and pitfalls you are aware of?

Thanks in advance.

Dan Hall
GE
Capital Solutions
Danbury, CT

T 513.217.5060
E dan.hall@ge.com
http://www.ge.com/capitalsolutions/

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








Normal

Normal
post from Jacques Dumouchel
"Jacques asked us to removed him from the list, and we did so before he
had a chance to send this post, so I'm sending it for him. If you want
to wish him luck, he is not longer on the list, so you can reach him at
Jacques.Dumouchel@ccra-adrc.gc.ca.
Laura Rochon
IUA


I would like to thank all the contributors to the list for their effort and valuable responses to all the questions. I joined the list when it started and I learned quite a few tricks over the year.
I was not one of the heavy contributors but some of you may remember seeing my name once in a while. I am retiring after spending 32+ years with the same company. I started working with IDMS in 1984(r5.7).It was a great product then and it is still a great DBMS.

I met several of you at CA conferences and at the IUA workshops and I did not meet anyone I did not like or would not have a beer with. I was even coerced into giving presentations at both events and I did not see anyone fall asleep, bonus.

Best of luck to all of you in your respective careers.
I will think about you but not too much while I spend the summer months riding my motorcycle.


Jacques Dumouchel
Canada Revenue Agency
Ottawa On Canada.

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








Normal

Normal
Postscript from the Mainframe
"Dear Listers -

I've been posed this question and don't know where to even begin..... I've never done anything like this.....

A client has a form that they print from an ADSO application.

The form is a pre-printed form and all the application does is format the data so that it lands in the proper boxes and lines on the pre-printed form.

They want to do away with the pre-printed form and have the data and all the original forms structure layout constructed and printed on a laser printer.

Has anyone been able to send Postscript or some other PCL / PDL language commands from an IDMS application that prints a form containing the forms layout structure along with any variable data to be printed?

Can this be done natively or do you need to use an Adobe product with Postscript or something else to accomplish this task?

Can the printer be defined to IDMS or does the print need to be routed somehow through a server?

Is this an easy thing to do and I'm just making this way harder than it really is?

Thanks.
Jon Gocher

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








Normal

Normal
Upgrade gotcha
"This will be of interest only to those who do dynamic DMCL changes,
which means varying a new copy of the DMCL without a CV outage:

For R12 and up, after you upgrade a CV to a new release, you cannot
dynamically implement a DMCL generated at the new release level, until
you have first implemented one non-dynamically, i.e. with an outage.
This was not an issue for us when we upgraded from R12 to R14.1 because
the DMCL's had to be recompiled anyway as part of the upgrade. But they
don't have to be recompiled as part of the R14.1 to R16 upgrade. Here
is the error message I got when I tried to vary the new copy of the
DMCL:

ERROR AUDITING/BUILDING THE NEW DMCL. BLDR RETURNED A STATUS OF 04. SEE
LOG.
RELEASE NUMBER OR OPSYS ID. CHANGED BETWEEN CURRENT DMCL AND NEW DMCL.

If you get caught by this during an unload/reload (as I did) you will
have to either leave the reloaded database offline until you can
schedule a CV outage, or back off the reload.

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
Re: [IDMSVENDOR-L] Upgrade gotcha
"kay - i seem to remember this coming up before on the list - i think the
solution was to zap something in memory so that the release number in
memory matched the new release # - but do not try this on the basis of my
(faulty at best) memory - check with CA or review the archives of this
list




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: Postscript from the Mainframe
"Jon,

The short answer is yes, we have an ADSO application that creates the form
layout etc and sends the PCL to an HP printer. The printer currently is
attached to an EBCDIC to ASCII converter box via a coax. This printer
configuration is being changed to be a VPS printer and connected to our
network. It is still defined to the CV as an IDMS printer with a print
class etc. The only change that was needed in the ADSO was to the work
record. The converter box escape sequences were changed to the PCL escape
in a hex format. I don't want to minimize the effort that was required by
the developer who orginally wrote the HP PCL. He did spend some time
figuring out how the PCL draws boxes and lines and how to position text.

Joe S Cates, C.C.P.
Database Analyst
Office of Global Access Technology
Montgomery County Public Schools
Rockville, MD 20850
email: Joe_Cates@fc.mcps.k12.md.us



IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM> writes:
Dear Listers -

I've been posed this question and don't know where to even begin.....
I've never done anything like this.....

A client has a form that they print from an ADSO application.

The form is a pre-printed form and all the application does is format the
data so that it lands in the proper boxes and lines on the pre-printed
form.

They want to do away with the pre-printed form and have the data and all
the original forms structure layout constructed and printed on a laser
printer.

Has anyone been able to send Postscript or some other PCL / PDL language
commands from an IDMS application that prints a form containing the forms
layout structure along with any variable data to be printed?

Can this be done natively or do you need to use an Adobe product with
Postscript or something else to accomplish this task?

Can the printer be defined to IDMS or does the print need to be routed
somehow through a server?

Is this an easy thing to do and I'm just making this way harder than it
really is?

Thanks.
Jon Gocher

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








Normal

Normal
Re: Postscript from the Mainframe
"Normally you use a VPS/DRS product to send postscript to the printer ; it
does not come out of an Ads appliction.

In the VPS product, you set it up so that the correct postscript needed is
sent to the printer each time you want it.

Dick

Richard C Borman/GIS/CSC
CSC/GIS Idms System Support
9305 Lightwave Ave
San Diego, Ca 92193-9011
home 760-787-1075
office 858-573-3265
rborman@csc.com



----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------





""Jon R. Gocher""
<jgocher To: IDMS-L@LISTSERV.IUASSN.COM
@FRONTIERNET.NET cc:
> Subject: Postscript from the Mainframe
Sent by: IDMS
Public
Discussion Forum
<IDMS-L


02/15/2006 07:18
AM
Please respond
to IDMS Public
Discussion Forum





Dear Listers -

I've been posed this question and don't know where to even begin..... I've
never done anything like this.....

A client has a form that they print from an ADSO application.

The form is a pre-printed form and all the application does is format the
data so that it lands in the proper boxes and lines on the pre-printed
form.

They want to do away with the pre-printed form and have the data and all
the original forms structure layout constructed and printed on a laser
printer.

Has anyone been able to send Postscript or some other PCL / PDL language
commands from an IDMS application that prints a form containing the forms
layout structure along with any variable data to be printed?

Can this be done natively or do you need to use an Adobe product with
Postscript or something else to accomplish this task?

Can the printer be defined to IDMS or does the print need to be routed
somehow through a server?

Is this an easy thing to do and I'm just making this way harder than it
really is?

Thanks.
Jon Gocher

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








Normal

Normal
Re: Upgrade gotcha
"Kay,

We've been here before and you'll probably find stuff in the list
archives.

The short version is you can cheat at this one by zapping the bit of
memory where the DMCL keeps his release number.

1) Do DCMT D AC XA PRO. Get the address of the DMCL.
2) Do DCMT D MEM ****** 200 at the address of the DMCL and you'll see
the release number (e.g. 1400) running around at 22 bytes into the control
block.
3) Do DCMT V MEM xxxxx ............ to change the release number to
whatever your DMCL to be varied in is and, finally ......
4) DCMT V DMCL NC will work just fine.

One thing I make a habit of when putting in a new release is to
generate/punch the DMCL after my upgrade even if I'm not changing
anything. On the next restart, I'll pick up the new control block and
everything will be matching up.

Alan Fields
VF Corporation
Greensboro, NC

336-424-4773
Alan_Fields@vfc.com


IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM> wrote on
02/15/2006 10:57:09 AM:
This will be of interest only to those who do dynamic DMCL changes,
which means varying a new copy of the DMCL without a CV outage:
For R12 and up, after you upgrade a CV to a new release, you cannot
dynamically implement a DMCL generated at the new release level, until
you have first implemented one non-dynamically, i.e. with an outage.
This was not an issue for us when we upgraded from R12 to R14.1 because
the DMCL's had to be recompiled anyway as part of the upgrade. But they
don't have to be recompiled as part of the R14.1 to R16 upgrade. Here
is the error message I got when I tried to vary the new copy of the
DMCL:
ERROR AUDITING/BUILDING THE NEW DMCL. BLDR RETURNED A STATUS OF 04. SEE
LOG.
RELEASE NUMBER OR OPSYS ID. CHANGED BETWEEN CURRENT DMCL AND NEW DMCL.
If you get caught by this during an unload/reload (as I did) you will
have to either leave the reloaded database offline until you can
schedule a CV outage, or back off the reload.
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
ERASE record ALL MEMBERS
"Hi all,

I'm hoping that someone already has a report to list all records and
sets needed for an ERASE record ALL MEMBERS, passing as parameter the
record name. We're getting a 0233 (on an ERASE record ALL MEMBERS)
in 2 different dialogs as something is missing in their respective
subschemas. Going thru the schema manually can be a long (and boring!)
process, so I'm hoping that someone already has a report to get the
information.

Thanks,
Laura Rochon
Ajilon Consulting

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








Normal

Normal
Re: [IDMSVENDOR-L] ERASE record ALL MEMBERS
"rather than finding the ""perfect"" list of areas, why not make a ""global""
subschema and use it ONLY for this program (pull the ERASE ALL MEMBERS
into a separate program to added security)

just a thought

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: ERASE record ALL MEMBERS
"Laura

If you generate the subschema's or a copy of it, it will tell you which
records cannot be be erased by using this subschema, then you check the
schema to check which sets that record exists in and then modify the
subschema.

Dennis Robock
Alberta Department of Energy

Outcomes