¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. H390-MVS
  2. Messages
Single Messages Topics Expanded Polls

Re: SYSCPK issues

 

Friends, tiso my problem to creat my test cics environment:

Ipl?

Imagem incorporada

d a,l

Imagem incorporada
CEDA
Imagem incorporada

This is my question.
How to creat? Transaction/ program, mapset, files to running my progran cics/vsam

Please help me.

hercules.conf



#
# Hercules Emulator Control file¡­
# Description:
# MaxShutdownSecs: 15
#
#
# System parameters
#

ARCHMODE z/Arch
ALRF ENABLE
cckd RA=2,RAQ=4,RAT=2,WR=2,GCINT=5,GCPARM=0,NOSTRESS=0,TRACE=0,FREEPEND=-1
CNSLPORT 3270
CONKPALV (3,1,10)
CPUMODEL 3090
CPUSERIAL 012345
DIAG8CMD ENABLE
ECPSVM YES
LOADPARM 0A95DC..
LPARNAME HERCULES
MAINSIZE 1024
MOUNTED_TAPE_REINIT DISALLOW
NUMCPU 4
OSTAILOR Z/OS
PANRATE 80
PGMPRDOS LICENSED
SHCMDOPT NODIAG8
SYSEPOCH 1900
TIMERINT 50
TZOFFSET +1400
YROFFSET 0

HERCPRIO 0
TODPRIO -20
DEVPRIO 8
CPUPRIO 0
PANTITLE z/OS 1.9 IPL A80?

# --------------------------------------------------------------
# SYMBOLS DEFINITION? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
# --------------------------------------------------------------

DEFSYM DASD "C:\Mainframe\Z_OS_110"
DEFSYM PRTR "C:\Mainframe\Z_OS_110"

# --------------------------------------------------------------
# Display Terminals
# --------------------------------------------------------------

0700 3270
0701 3270
0702 3270
0703 3270
0704 3270

# --------------------------------------------------------------
# DASD Devices
# --------------------------------------------------------------

0A81 3390 c:\cckd/zares1.cckd sf=c:\shadow/zares1_*
0A82 3390 c:\cckd/zares2.cckd sf=c:\shadow/zares2_*
0A83 3390 c:\cckd/zadb81.cckd sf=c:\shadow/zadb81_*
0A84 3390 c:\cckd/zadb82.cckd sf=c:\shadow/zadb82_*
0A85 3390 c:\cckd/zadb83.cckd sf=c:\shadow/zadb83_*
0A86 3390 c:\cckd/zadb84.cckd sf=c:\shadow/zadb84_*
0A87 3390 c:\cckd/zadb91.cckd sf=c:\shadow/zadb91_*
0A88 3390 c:\cckd/zadb92.cckd sf=c:\shadow/zadb92_*
0A89 3390 c:\cckd/zacic1.cckd sf=c:\shadow/zacic1_*
0A8A 3390 c:\cckd/zadis1.cckd sf=c:\shadow/zadis1_*
0A8B 3390 c:\cckd/zadis2.cckd sf=c:\shadow/zadis2_*
0A8C 3390 c:\cckd/zadis3.cckd sf=c:\shadow/zadis3_*
0A8D 3390 c:\cckd/zadis4.cckd sf=c:\shadow/zadis4_*
0A8E 3390 c:\cckd/zadis5.cckd sf=c:\shadow/zadis5_*
0A8F 3390 c:\cckd/zadis6.cckd sf=c:\shadow/zadis6_*
0A90 3390 c:\cckd/zaims1.cckd sf=c:\shadow/zaims1_*
0A91 3390 c:\cckd/zaprd1.cckd sf=c:\shadow/zaprd1_*
0A92 3390 c:\cckd/zaprd2.cckd sf=c:\shadow/zaprd2_*
0A93 3390 c:\cckd/zaprd3.cckd sf=c:\shadow/zaprd3_*
0A94 3390 c:\cckd/zaprd4.cckd sf=c:\shadow/zaprd4_*
0A95 3390 c:\cckd/zasys1.cckd sf=c:\shadow/zasys1_*
0A96 3390 c:\cckd/zauss1.cckd sf=c:\shadow/zauss1_*
0A97 3390 c:\cckd/zawas1.cckd sf=c:\shadow/zawas1_*
0A98 3390 c:\cckd/zawas2.cckd sf=c:\shadow/zawas2_*
0A99 3390 c:\cckd/zawas3.cckd sf=c:\shadow/zawas3_*
0A9A 3390 c:\cckd/sares1.cckd sf=c:\shadow/sares1_*


Em quinta-feira, 25 de junho de 2020 07:36:51 BRT, Joe Monk <joemonk64@...> escreveu:


While Jay Moseley does not need defending, the procedure was written to be compatible with his MVS build.

If you are using his procedure?with another system like TK3UPD (which last I heard has questionable legs anyway, because Phil decided to claim copyright over the whole thing), of there will be a need to modify the install procedures.

So, when viewed thru that lens, none of these changes are either unusual or unnecessary. Every system takes some customization.

Joe

On Wed, Jun 24, 2020 at 9:30 PM Drew Derbyshire <swhobbit@...> wrote:

I had various issues with SYSCPK install and contents.

First, the changes to the JES2 procedure:

  • #1 with a bullet
    • This (as suggested on ) won't work:
      ??? S JES2OLD
      JES2OLD is not a registered subsystem, and thus the START command will hang.
  • The JES2 procedure is not modified in a consistent style with the preexisting statements:
    • SYSC.PROCLIB was hardcoded, unlike SYS1.PROCLIB and SYS2.PROCLIB.?
    • When combined with #1 above and a user mistake by me (!), my recovery entailed restoring from my nightly backups.?
      • The preferred (and recoverable from) method of adding the PROCLIB would have been:
      • Adding parameters PC= and VC= (for volume) to the new library
      • I would also suggest also use of UNIT=SYSDA, not UNIT=3350.
  • SYSC.PROCLIB was in front of SYS1.PROCLIB
    • This is not acceptable (not on my system!), and a bad practice in general.? End of the (DD) line, please.
    • You could add an alternate PROCLIB DD (/*JOBPARM PROCLIB=SYSC?)
    • Are there duplicate names between SYS1.PROCLIB AND SYSC.PROCLIB?
  • On a system with dynamic PROCLIB support, is adding SYSC.PROCLIB directly to JES2 needed at all?? (At cost of an additional line of JCL, of course.)

SYSC.LINKLIB has multiple minor issues:

  • The library seems to be dumping ground for multiple module types; I would suggest it be audited and replaced with:
    • A library for executable language components (under the current name?)
      • Is there a summary of changes for modules which also in SYS1.LINKLIB?
    • A library for executable utilities
    • A library for linkable subroutines
  • Adding SYSC.LINKLIB with its 905 members (SYS1.LINKLIB only has 121) to the APF authorized list is somewhat cavalier.?
    • Is there a summary of what modules need authorization (and why)?
    • I would think once reorganized, only the utilities library needs APF authorization?

And finally, the VATLST modifier didn't detect SYSCPK was already added to VATLST00, and inserted a duplicate entry.? As (I think) that was the only line modified, the entire step should have been skipped. (Do the other steps have duplicate changes issues as well?

-- 
Drew Derbyshire

Mobile: 425-471-8183

"The only thing necessary for the triumph of evil is for good men to do
 nothing."

Join [email protected] to automatically receive all group messages.