ca.portal.admin

Re:Data encryption

Discussion created by ca.portal.admin on May 15, 2009
Hi all,
One of my clients just approached me about data encryption. They want to
encrypt ""sensitive"" data such as SSN and account numbers. I would like =
to
ask the list if anyone is using encryption and their thoughts
recommendations and/or opinions.

Thanks
Brian

The information contained in this e-mail, and any attachment, is
confidential and is intended solely for the use of the intended =
recipient.
Access, copying or re-use of the e-mail or any attachment, or any
information contained therein, by any other person is not authorized. If =
you
are not the intended recipient please return the e-mail to the sender =
and
delete it from your computer. Although we attempt to sweep e-mail and
attachments for viruses, we do not guarantee that either are virus-free =
and
accept no liability for any damage sustained as a result of viruses.

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain
disclosures relating to European legal entities.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Data encryption
"Hi all,
One of my clients just approached me about data encryption. They want to
encrypt ""sensitive"" data such as SSN and account numbers. I would like to
ask the list if anyone is using encryption and their thoughts
recommendations and/or opinions.

Thanks
Brian

The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses.

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Missing posting for RHDCUXIT resolution.
"Hello Moderators:



I posted a resolution to my RHDCUXIT problem over the weekend and I received
two E-mails from people directly and when I asked them if they saw my post
they both replied no? The only message that I received was that the message
was submitted to the moderators?



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Missing posting for RHDCUXIT resolution.
"Hello Moderators:



I posted a resolution to my RHDCUXIT problem over the weekend and I received
two E-mails from people directly and when I asked them if they saw my post
they both replied no? The only message that I received was that the message
was submitted to the moderators?



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: DCPROFIL and system mode user exits PROBLEM RESOLVED
"Hello All:



I made a mistake, alert the media, LOL. I put together the assembly and link
edit of RHDCUXIT outside of SMP/E because I have seven IDMS Regions and they
all don't use the same toolkit products.



The mistake that I made was that I failed to put an INCLUDE in the link edit
of the RHDCUXIT for the source code that I had just assembled in the
previous step.



All is well now and now and I have to go back to the other client site and
fix that one as well.



Many thanks to Ed Mckinney his explanation of the problem made me look at
the assembly and link edit much closer and that's when I found it.



I like the new display only showing what you are actually using.



* SYSTEM/USER EXITS *


EXIT CALL NEED TO ENTRY
POINT/

NUMBER DEFINED MODE CONVENTIONS LOAD AMODE MODULE
NAME




000 YES SYSTEM DC NO ANY 00110E38


004 YES SYSTEM DC NO ANY 00112568


005 YES SYSTEM DC NO ANY 001134F0


006 YES SYSTEM DC NO ANY 00115598


013 YES SYSTEM DC NO ANY 0010F6F8


014 YES SYSTEM DC NO ANY 0010F410


015 YES SYSTEM DC NO ANY 0010FEA0


017 YES SYSTEM DC NO ANY 0010EE5C


018 YES SYSTEM DC NO ANY 0010EEB8


033 YES SYSTEM DC NO ANY 00111AE8


333 YES SYSTEM DC NO ANY 00114A88




William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296

_____

From: Mckinney, Edward F [mailTo:Edward.Mckinney@ca.com]
Sent: Saturday, May 16, 2009 3:14 PM
To: archcons@bellsouth.net
Subject: RE: DCPROFIL and system mode user exits



Bill, The exit modules may be linked into the RHDCUXIT module, but not
deined to RHDCUXIT via the #DEFXIT macro as assembly time. DCPROFIL walks
the exit module looking for the #DEFXIT assembler... check to see if you
coded the #DEFXITs in the RHDCUXIT assemble.. 17 and 18 are default exit
stubs distributed in the RHDCUXIT source.

Ed McK.



_____

From: IDMS Public Discussion Forum on behalf of William M. Allen, Jr.
Sent: Fri 5/15/2009 5:08 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: DCPROFIL and system mode user exits

Hello All:



I have done two different 16.0 SP7 installations and I get the same results
at each site.



When I issue a DCPROFIL it only shows me two exits 17 & 18?



When I issue a LOOK PROGRAM=RHDCUXIT I see all the exits for the toolkit
installed.



Is there an issue with DCPROFIL & 16.0 SP7.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: DCPROFIL and system mode user exits PROBLEM RESOLVED
"Hello All:



I made a mistake, alert the media, LOL. I put together the assembly and link
edit of RHDCUXIT outside of SMP/E because I have seven IDMS Regions and they
all don't use the same toolkit products.



The mistake that I made was that I failed to put an INCLUDE in the link edit
of the RHDCUXIT for the source code that I had just assembled in the
previous step.



All is well now and now and I have to go back to the other client site and
fix that one as well.



Many thanks to Ed Mckinney his explanation of the problem made me look at
the assembly and link edit much closer and that's when I found it.



I like the new display only showing what you are actually using.



* SYSTEM/USER EXITS *


EXIT CALL NEED TO ENTRY
POINT/

NUMBER DEFINED MODE CONVENTIONS LOAD AMODE MODULE
NAME




000 YES SYSTEM DC NO ANY 00110E38


004 YES SYSTEM DC NO ANY 00112568


005 YES SYSTEM DC NO ANY 001134F0


006 YES SYSTEM DC NO ANY 00115598


013 YES SYSTEM DC NO ANY 0010F6F8


014 YES SYSTEM DC NO ANY 0010F410


015 YES SYSTEM DC NO ANY 0010FEA0


017 YES SYSTEM DC NO ANY 0010EE5C


018 YES SYSTEM DC NO ANY 0010EEB8


033 YES SYSTEM DC NO ANY 00111AE8


333 YES SYSTEM DC NO ANY 00114A88




William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296

_____

From: Mckinney, Edward F [mailTo:Edward.Mckinney@ca.com]
Sent: Saturday, May 16, 2009 3:14 PM
To: archcons@bellsouth.net
Subject: RE: DCPROFIL and system mode user exits



Bill, The exit modules may be linked into the RHDCUXIT module, but not
deined to RHDCUXIT via the #DEFXIT macro as assembly time. DCPROFIL walks
the exit module looking for the #DEFXIT assembler... check to see if you
coded the #DEFXITs in the RHDCUXIT assemble.. 17 and 18 are default exit
stubs distributed in the RHDCUXIT source.

Ed McK.



_____

From: IDMS Public Discussion Forum on behalf of William M. Allen, Jr.
Sent: Fri 5/15/2009 5:08 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: DCPROFIL and system mode user exits

Hello All:



I have done two different 16.0 SP7 installations and I get the same results
at each site.



When I issue a DCPROFIL it only shows me two exits 17 & 18?



When I issue a LOOK PROGRAM=RHDCUXIT I see all the exits for the toolkit
installed.



Is there an issue with DCPROFIL & 16.0 SP7.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: DCPROFIL and system mode user exits PROBLEM RESOLVED
"Bill (and all) - different RHDCUXIT configurations are not a problem to
SMP/E

1) create a separate PPOPTION member for each configuration

for example RHDCUXLV and RHDCUXGB

2) set up a MASTER usermod to set up the linkedit templates

(jobcard)
//*
//STEP1 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPPTFIN DD DATA,DLM='%%'
++USERMOD(USRXITJ)
DESC(CREATE THE TEMPLATE USER EXIT LIST LOAD MODULE).
++VER(Z038) FMID(CGJH024).
++JCLIN.
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS IS
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.DBALOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXLV)
INCLUDE DISTLOAD(UT02EXIT)
INCLUDE DISTLOAD(UT23EXIT)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUXLD(R)
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS IS
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.TESTLOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXLV)
INCLUDE DISTLOAD(UT02EXIT)
INCLUDE DISTLOAD(UT23EXIT)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUXLT(R)
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS IS
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.PRODLOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXLV)
INCLUDE DISTLOAD(UT02EXIT)
INCLUDE DISTLOAD(UT23EXIT)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUXLP(R)
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS I
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.V01LOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXGB)
INCLUDE DISTLOAD(RHDCUX01)
INCLUDE DISTLOAD(RHDCUX02)
INCLUDE DISTLOAD(RHDCUX18)
INCLUDE DISTLOAD(RHDCUX28)
INCLUDE DISTLOAD(RHDCUX29)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUG01(R)
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS I
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.V51LOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXGB)
INCLUDE DISTLOAD(RHDCUX01)
INCLUDE DISTLOAD(RHDCUX02)
INCLUDE DISTLOAD(RHDCUX18)
INCLUDE DISTLOAD(RHDCUX28)
INCLUDE DISTLOAD(RHDCUX29)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUG51(R)


the above example shows the 2 different source versions set up for 5
different loadlibs (for 5 different CVs or groups of CVs)
each usermod loadlib (TESTLOAD, PRODLOAD, V51LOAD) were previously defined
to SMP/E


then - create the ""work"" usermods to actually assemble and link-edit the
modules

(jobcard)
//*
//STEP1 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPPTFIN DD DATA,DLM='%%'
++USERMOD(USREXLV)
DESC(CREATE THE LV USER EXIT LIST LOAD MODULE).
++VER(Z038) FMID(CGJH024).
++SRC(RHDCUXLV) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION) .
++SRC(UT02EXIT) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION) .
++SRC(UT23EXIT) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION) .
%%
//SMPCNTL DD *
SET BOUNDARY(GLOBAL).
RECEIVE SELECT(USREXLV) /* <=== USERMOD NAME HERE */.
SET BOUNDARY(IDMSTGT).
APPLY CHECK SELECT(USREXLV) .
/*
//STEP2 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U',COND=(4,LT)
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPCNTL DD *
SET BOUNDARY(IDMSTGT).
APPLY SELECT(USREXLV) .
/*

the above JCL actually causes the RHDCUXIT to be linked multiple times -
based the on the template above: since the ++SRC here references RHDCUXLV
- each occurance in the template of
INCLUDE DISTLOAD(RHDCUXLV) will cause a separate link/edit to occur - also
SMP/E cannot allow the same NAME to be used in multiple LINK/EDITS (even
to different loadlibs) - but the same ALIAS can be used in mutiple
loadlibs - thus the IDMS system will find a RHDCUXIT (albeit an alias) in
each loadlib

similarly,
this ""work"" usermod will install the other RHDCUXIT module in the same
way:

//CMH5342A JOB (T4340,0427,UT9999),CLASS=D,MSGCLASS=X, ,
// NOTIFY=CMH5342
//STEP1 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPPTFIN DD DATA,DLM='%%'
++USERMOD(USREXGB)
DESC(CREATE THE GB USER EXIT LIST LOAD MODULE).
++VER(Z038) FMID(CGJH024) /*******************************/
/* SUPPLY THE FMID WHICH IS */
/* ASSOCIATED WITH THE MODULE */
/* YOU ARE CUSTOMIZING. */
/*******************************/.
++SRC(RHDCUXGB) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX01) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX02) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX18) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX28) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX29) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
%%
//SMPCNTL DD *
SET BOUNDARY(GLOBAL).
RECEIVE SELECT(USREXGB) /* <=== USERMOD NAME HERE */.
SET BOUNDARY(IDMSTGT).
APPLY CHECK SELECT(USREXGB) .
/*
//STEP2 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U',COND=(4,LT)
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPCNTL DD *
SET BOUNDARY(IDMSTGT).
APPLY SELECT(USREXGB) .
/*

again - specifying ++SRC(RHDCUXGB) DISTLIB(DISTSRC) DISTMOD(DISTLOAD)
TXLIB(PPOPTION). in the ""work"" usermod triggers a link-edit for EVERY
template entry with INCLUDE DISTLOAD(RHDCUXGB) and place the load
module in the user-defined load library specified by //SYSLMOD


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

you only need to test the programs that you want to work correctly




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 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] DCPROFIL and system mode user exits PROBLEM RESOLVED
"Bill (and all) - different RHDCUXIT configurations are not a problem to
SMP/E

1) create a separate PPOPTION member for each configuration

for example RHDCUXLV and RHDCUXGB

2) set up a MASTER usermod to set up the linkedit templates

(jobcard)
//*
//STEP1 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPPTFIN DD DATA,DLM='%%'
++USERMOD(USRXITJ)
DESC(CREATE THE TEMPLATE USER EXIT LIST LOAD MODULE).
++VER(Z038) FMID(CGJH024).
++JCLIN.
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS IS
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.DBALOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXLV)
INCLUDE DISTLOAD(UT02EXIT)
INCLUDE DISTLOAD(UT23EXIT)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUXLD(R)
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS IS
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.TESTLOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXLV)
INCLUDE DISTLOAD(UT02EXIT)
INCLUDE DISTLOAD(UT23EXIT)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUXLT(R)
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS IS
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.PRODLOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXLV)
INCLUDE DISTLOAD(UT02EXIT)
INCLUDE DISTLOAD(UT23EXIT)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUXLP(R)
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS I
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.V01LOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXGB)
INCLUDE DISTLOAD(RHDCUX01)
INCLUDE DISTLOAD(RHDCUX02)
INCLUDE DISTLOAD(RHDCUX18)
INCLUDE DISTLOAD(RHDCUX28)
INCLUDE DISTLOAD(RHDCUX29)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUG01(R)
//CAIDMS JOB (12345),'CA-IDMS/DB INSTALL' THIS JOB CARD OK AS I
//RHDCUXIT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.V51LOAD,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(RHDCUXGB)
INCLUDE DISTLOAD(RHDCUX01)
INCLUDE DISTLOAD(RHDCUX02)
INCLUDE DISTLOAD(RHDCUX18)
INCLUDE DISTLOAD(RHDCUX28)
INCLUDE DISTLOAD(RHDCUX29)
INCLUDE DISTLOAD(USG2333)
ENTRY UXITEP1
MODE RMODE(24),AMODE(31)
ALIAS RHDCUXIT(UXITEP1)
NAME RHDCUG51(R)


the above example shows the 2 different source versions set up for 5
different loadlibs (for 5 different CVs or groups of CVs)
each usermod loadlib (TESTLOAD, PRODLOAD, V51LOAD) were previously defined
to SMP/E


then - create the ""work"" usermods to actually assemble and link-edit the
modules

(jobcard)
//*
//STEP1 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPPTFIN DD DATA,DLM='%%'
++USERMOD(USREXLV)
DESC(CREATE THE LV USER EXIT LIST LOAD MODULE).
++VER(Z038) FMID(CGJH024).
++SRC(RHDCUXLV) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION) .
++SRC(UT02EXIT) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION) .
++SRC(UT23EXIT) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION) .
%%
//SMPCNTL DD *
SET BOUNDARY(GLOBAL).
RECEIVE SELECT(USREXLV) /* <=== USERMOD NAME HERE */.
SET BOUNDARY(IDMSTGT).
APPLY CHECK SELECT(USREXLV) .
/*
//STEP2 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U',COND=(4,LT)
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPCNTL DD *
SET BOUNDARY(IDMSTGT).
APPLY SELECT(USREXLV) .
/*

the above JCL actually causes the RHDCUXIT to be linked multiple times -
based the on the template above: since the ++SRC here references RHDCUXLV
- each occurance in the template of
INCLUDE DISTLOAD(RHDCUXLV) will cause a separate link/edit to occur - also
SMP/E cannot allow the same NAME to be used in multiple LINK/EDITS (even
to different loadlibs) - but the same ALIAS can be used in mutiple
loadlibs - thus the IDMS system will find a RHDCUXIT (albeit an alias) in
each loadlib

similarly,
this ""work"" usermod will install the other RHDCUXIT module in the same
way:

//CMH5342A JOB (T4340,0427,UT9999),CLASS=D,MSGCLASS=X, ,
// NOTIFY=CMH5342
//STEP1 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPPTFIN DD DATA,DLM='%%'
++USERMOD(USREXGB)
DESC(CREATE THE GB USER EXIT LIST LOAD MODULE).
++VER(Z038) FMID(CGJH024) /*******************************/
/* SUPPLY THE FMID WHICH IS */
/* ASSOCIATED WITH THE MODULE */
/* YOU ARE CUSTOMIZING. */
/*******************************/.
++SRC(RHDCUXGB) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX01) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX02) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX18) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX28) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
++SRC(RHDCUX29) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
%%
//SMPCNTL DD *
SET BOUNDARY(GLOBAL).
RECEIVE SELECT(USREXGB) /* <=== USERMOD NAME HERE */.
SET BOUNDARY(IDMSTGT).
APPLY CHECK SELECT(USREXGB) .
/*
//STEP2 EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U',COND=(4,LT)
//SMPCSI DD DISP=SHR,DSN=IDMSS.R170.CSI
//SMPHOLD DD DUMMY
//SMPCNTL DD *
SET BOUNDARY(IDMSTGT).
APPLY SELECT(USREXGB) .
/*

again - specifying ++SRC(RHDCUXGB) DISTLIB(DISTSRC) DISTMOD(DISTLOAD)
TXLIB(PPOPTION). in the ""work"" usermod triggers a link-edit for EVERY
template entry with INCLUDE DISTLOAD(RHDCUXGB) and place the load
module in the user-defined load library specified by //SYSLMOD


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

you only need to test the programs that you want to work correctly




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: Data encryption
"We implemented encryption into our production environment back in September of 2008.
In response to an audit we needed to encrypt SSN data on our database.
The implementation is accomplished via 2 database procedures written in assembler.

There are several of encryption issues you need to be aware of;

For existing data, implementation has to be a multi-step process.
The database procedure for encryption has to be added to the schema first then
each record must be read and written to encrypt the data on the DB.
Then the decryption procedure can be added to the schema.

If the encrypted field takes part in an index your index will be shot unless you
use some sort of sorted encryption key. Of course a sort able encryption
key is easier to crack which sort of defeats the purpose of encryption.

None of our keys were calc keys but if on a write you pass the DBMS an encrypted calc key then
you would need to encrypt it again before each read.

I did some measurements and there is some additional CPU overhead involved since you
are twiddling some bits in the encryption/decryption routines.

Terry Schwartz

Outcomes