ca.portal.admin

Re:Re: Causes of a DC273912 Message

Discussion created by ca.portal.admin on Jul 18, 2008
Chris, If you have the 'NODYNAMIC' option specified for the program,
then you can't have multiple versions. Try specifying DYNAMIC for the
program statement.
=20
From the Sysgen Manual:
DYNamic

Allows users to define additional versions of the program at runtime
either by

means of the DCMT VARY DYNAMIC PROGRAM command or, if the program

is eligible for automatic definition, through the definition of null
PDEs on the

SYSTEM statement.

DYNAMIC is the default when you specify neither DYNAMIC nor

NODYNAMIC in the PROGRAM statement.

NODynamic

Prevents users from defining additional versions of the program at
runtime.

Additionally, the system generation compiler ensures that only one
version of the

program is included in the system definition.

Bob
=20
Bob Wiklund
Tiburon Technologies
623 594-6022

________________________________

From: IDMS 3rd-party providers forum on behalf of Chris Wood
Sent: Fri 7/18/2008 11:16 AM
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Subject: Causes of a DC273912 Message



Hi,

=3D20

We are running 16.0 SP1 + many apars on z/OS 1.8 and have a need to
create a non-version 1 DC-COBOL program to test an emergency that only
happens in Production. When we try the DCMT VDP it threw a DC273912 V1
Multiple Versions of program XXXXXXXX are not allowed. Entering DCMT D
MESS DC273912 we get this The user attempted to add a program definition
dynamically, but the program is defined at system generation time with
the MULTIPLE VERSIONS NOT ALLOWED attribute. This does not appear in the
syntax for Program or System in the sysgen. We can do this on
Development where we use multiple versions but can't seem to get a
handle on where we have defined this in Production. =3D20

=3D20

Anyone know the magic sysgen parameter that we must have set differently
in production to development?

=3D20

Thanks

=3D20

Chris Wood

Alberta Department of Energy

CANADA =3D20

=3D20

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
"
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: IDMS Password Length Limited to 8 characters
"I vote you try telling your security folk you can't access the dictionary
until you get past a RACF signon (true), so the IDMS password strength is
superfluous.

Then hide your cheat sheet somewhere they can't find it. I actually use
""code"" on my cheat sheet... I recycle common phrases in different orders and
then write down only a mnemonic key. For example: if I use ""Giraffe"", my
zip code, and a particular Cal football score, I write ""GZ120108"" (120108
being the date of a particular game) instead of GIRAFFE945211230(the latter
being a 12-30 loss to Stanford on 12/1/08, of all things). If I replace the
""i"" in Giraffe with a ""1"", I write it down as ""G1"". Replacing 'i's with
'1's, 'o's with '0's, 'e's with '3's helps you keep actual words while at
the same time sticking numbers in.

Next cycle it might be Z123108G1 (a win 42-36 win over Air Force on
12/31/08) yielding 945214236G1raffe.

No, those are examples, my real passwords are something else.

For simpler systems the passwords might be GZ or G1 or....

Other options are to use a particular class of objects (animals in the above
example, could be cars or movie stars or brands/types of beer) and move up
the alphabet with each new password (""Hippopotamus"" replacing ""Giraffe"",
""Porter"" replacing ""Okocim"", ""Prius"" replacing ""Oldsmobile"").

Yours in paranoia....

* DQC

Outcomes