On 2016-01-25 11:24, Skip Robinson wrote: > > -- Here's a serious inhibitor for some shops. Despite decades of advice to > the contrary, some shops still share application load libraries across > sysplex boundaries. This practice dates back to pre-sysplex configurations. > In our case, in our test environment, we share load libraries across sysplex boundaries because we have more systems at a wider range of releases than sysplex supports. (We support OS releases at more levels than IBM. Many ISVs do likewise; it's our added value.)
> While sharing a PDS in this way is risky, sharing a PDSE among sysplexes is > What are the risks to sharing a PDS that way? AFAIK, z/OS for many releases has provided serialization of PDS directory updates. This avoids directory corruption. Otherwise, it's the responsibility of an administrator to assure that all updates of shared PDS are performed from a single system, or otherwise serialized. > a recipe for disaster because only sysplex understands PDSE. It's not GRS or > ISV equivalent; it's sysplex itself. (I don't know the technicality of this > limitation.) You cannot just convert a shared PDS to a PDSE. You have to > change your application load module management practices to support multiple > targets. If you have product or RYO code that migrates a load module from > DEV to PROD, you have to change the process to migrate from DEV to PROD1, > PROD2, ... PRODn. Depending on your configuration and migration process, > this could be a big deal. This change has to be completed before the first > COBOL V5 load module moves to production. > AFAIK, NFS suffers no such restrictions or risks. I'd welcome support of //STEPLIB DD PATH='/...' and similar for LINKLIST. UNIX executables support Program Objects. IBM should consider this as a solution. Can COBOL v5 objects be bound into UNIX files? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
