Re: I am getting IEW2606S in HEWL despite the fact that the target library IS PDSE

2017-09-03 Thread Wayne Bickerdike 
Dave has identified the problem. SYSLMOD needs DSNTYPE=LIBRARY.

If you use SCLM, the supplied linkedit language definition also lacks
DSNTYPE=LIBRARY.

IBM are a bit amiss here because SCLM uses an intermediate load library to
copy the resultant load module and this defaults to a PDS.

Took me a few days to work this out.

On Mon, Sep 4, 2017 at 3:01 PM, David Crayford  wrote:

> Good job Lizette!
>
> Is the SYSLMOD output data set a PDSE? I can't see a DSNTYPE=LIBRARY in
> the JCL.
>
>
>
> On 4/09/2017 12:55 PM, Lizette Koehler wrote:
>
>> I tried to reformat this so it is easier to read.  One thing I do is
>> place a couple of blanks at the beginning of the line when I have a list I
>> am producing.  It sometimes help to keep the lines individual rather than
>> mashed together.
>>
>> Let me know if I incorrectly formatted the Options or LKED JCL.
>>
>> Thanks
>>
>> Lizette
>>
>>
>> -Original Message-
>>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>>> Behalf Of Ze'ev Atlas
>>> Sent: Sunday, September 03, 2017 8:34 PM
>>> To: IBM-MAIN@LISTSERV.UA.EDU
>>> Subject: I am getting IEW2606S in HEWL despite the fact that the target
>>> library IS PDSE
>>>
>>> Hi allI am compiling and linking a bunch of C programs using ZOS V2.2
>>> z/OS XL
>>> C and z/OS V2 R2 BINDER.  Most compile and link without any issue
>>> despite the
>>> fact that I have and use longnames.  I am getting IEW2606S in HEWL for
>>> three
>>> of these programs despite the fact that the target library IS PDSE.
>>> Please
>>> see if you have any clue why would that happen IEW2606S 4B39 MODULE
>>> INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND CANNOT BE SAVED IN
>>> LOAD
>>> MODULE FORMAT.
>>>
>>>   I use the same options for all the programs.
>> Compile options:
>>*NOGONUMBER
>>*NOALIAS
>>*NORENT
>>*TERMINAL
>>*NOUPCONV
>>*SOURCE
>>*NOLIST
>>*NOXREF
>>*NOAGG
>>*NOPPONLY
>>*NOEXPMAC
>>*NOSHOWINC
>>*NOOFFSET
>>*MEMORY
>>*S
>> SCOMM
>>*NOSHOWMACROS
>>*SKIPSRC(SHOW)
>>*NOREPORT
>>*NOMAKEDEP
>>*PREFETCH
>>*THREADED
>>*LONGNAME
>>*START
>>*EXECOPS
>>*ARGPARSE
>>*NOEXPO
>> RTALL
>>*NODLL(NOCALLBACKANY
>>*NOLIBANSI
>>*NOWSIZEOF
>>*REDIR
>>*ANSIALIAS
>>*DIG
>> RAPH
>>*NOROCONST
>>*ROSTRIN
>>*TUNE(8)
>>*ARCH(8)
>>*SPILL(128)
>>*MAXMEM(2097152)
>>*NOCOMPACT
>>*TARGET(LE,CURRENT)
>>*FLAG(I)
>>*NOTEST(SYM,BLOCK,LINE,PATH,HOOK)
>>*NOOPTIM
>>*NOINLINE(AUTO,NOREPORT,100,1000)
>>*NESTINC(255)
>>*BITFIELD(UNSIGNED)
>>*NOINFO
>>*NODFP
>>*NOVECTOR
>>*FLOAT(HEX,FOLD,NO
>> MAF,AFP(NOVOLATILE))
>>*STRICT
>>*NOCOMPRES
>>*NOSTRICT_INDUCTION
>>*AGGRCOPY(NOOVERLAP)
>>*CHARS(UNSIGNED)
>>*NOIGNERR
>> NO
>>*NOINI
>> TAUTO
>>*CSECT(CONVERT2)
>>*NOEVENTS
>>*ASSERT(RESTRICT)
>>*NORESTRICT
>>*OBJECT
>>*NOGENASM
>>*OPTFILE(DD:OPTFILE)
>>*NOSERVICE
>>*NOOE
>>*NOIPA
>>*SEARCH(//'CEE.SCEEH.+')
>>*NOLSEARCH
>>*NOLOCALE
>>*HALT(16)
>>*PLIST(HOST)
>>*NOCONVLIT
>>*NOASCII
>>*GOFF
>>*ILP32
>>*NOWARN64
>>*NOHGPR
>>*NOHOT
>>*NOMETAL
>>*NOARMOD
>>*NOXPLINK(NOBACKCHAIN,NOSTOREARGS,NOCALLBACK,GUARD,OSCALL(NOSTACK))
>>*ENUMSIZE(SMALL)
>>*NOHALTONMSG
>>*NOSUPPRESS
>>*NORTCHECK
>>*NODEBUG
>>*NOSQL
>>*NOCICS
>>*UNROLL(AUTO)
>>*KEYWORD()
>>*NOKEYWORD(asm,typeof)
>>*NOSEVERITY
>>*NODSAUSER
>>*NOINCLUDE
>>*NOSMP
>>*SYSSTATE(NOASCENV,OSREL(NONE))
>>*NOFUNCEVENT
>>*NOASM
>>*NOASMLIB
>>
>>DEFINE(HAVE_CONFIGH=1)
>>DEFINE(HAVE_STDINT_H=1)
>>DEFINE(_XOPEN_SOURCE=1)
>>DEFINE(_POSIX_SOURCE=1)
>>UNDEFINE(__cplusplus)
>>DEFINE(PCRE2_CODE_UNIT_WIDTH=8)
>>DEFINE(NATIVE_ZOS=1)
>>DEFINE(EBCDIC=1)
>>UNDEFINE(SUPPORT_JIT)
>>UNDEFINE(NATIVE_ZOS_POSIX)
>>
>> The linkage step looks like:
>> XX*--
>> XX* LINKEDIT STEP:
>> XX*--
>> IEFC653I SUBSTITUTION JCL - UNIT=SYSALLDA,SPACE=(32000,(30,30)),DCB=(
>>//USERLIB  DD DSN=,DISP=SHR
>>IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.SRCE,DISP=SHR
>>//COMPILE.SYSCRPT DD SYSOUT=*
>>//OPTFILE DD DSN=(OPTFILE),DISP=SHR
>>IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.JCLLIB(OPTFILE),DISP=SHR
>>XXLKED   EXEC PGM=HEWL,COND=(4,LT,COMPILE),R
>> EGION=,PARM=''
>> IEFC653I SUBSTITUTION JCL - PGM=HEWL,COND=(4,LT,COMPILE),REGION=1024K
>>//LKED.SYSLIB  DD
>>X/SYSLIB   DD  DSNAME=,DISP=SHR
>>IEFC653I SUBSTITUTION JCL - DSNAME=CEE.SCEELKED,DISP=SHR
>>//DD DSN=,DISP=SHR
>>IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.LOADLIB,DISP=SHR
>>XXSYSPRINT DD  SYSOUT=*
>>

Re: I am getting IEW2606S in HEWL despite the fact that the target library IS PDSE

2017-09-03 Thread David Crayford 

Good job Lizette!

Is the SYSLMOD output data set a PDSE? I can't see a DSNTYPE=LIBRARY in 
the JCL.



On 4/09/2017 12:55 PM, Lizette Koehler wrote:

I tried to reformat this so it is easier to read.  One thing I do is place a 
couple of blanks at the beginning of the line when I have a list I am 
producing.  It sometimes help to keep the lines individual rather than mashed 
together.

Let me know if I incorrectly formatted the Options or LKED JCL.

Thanks

Lizette



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Ze'ev Atlas
Sent: Sunday, September 03, 2017 8:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: I am getting IEW2606S in HEWL despite the fact that the target
library IS PDSE

Hi allI am compiling and linking a bunch of C programs using ZOS V2.2 z/OS XL
C and z/OS V2 R2 BINDER.  Most compile and link without any issue despite the
fact that I have and use longnames.  I am getting IEW2606S in HEWL for three
of these programs despite the fact that the target library IS PDSE.  Please
see if you have any clue why would that happen IEW2606S 4B39 MODULE
INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND CANNOT BE SAVED IN LOAD
MODULE FORMAT.


  I use the same options for all the programs.
Compile options:
   *NOGONUMBER
   *NOALIAS
   *NORENT
   *TERMINAL
   *NOUPCONV
   *SOURCE
   *NOLIST
   *NOXREF
   *NOAGG
   *NOPPONLY
   *NOEXPMAC
   *NOSHOWINC
   *NOOFFSET
   *MEMORY
   *S
SCOMM
   *NOSHOWMACROS
   *SKIPSRC(SHOW)
   *NOREPORT
   *NOMAKEDEP
   *PREFETCH
   *THREADED
   *LONGNAME
   *START
   *EXECOPS
   *ARGPARSE
   *NOEXPO
RTALL
   *NODLL(NOCALLBACKANY
   *NOLIBANSI
   *NOWSIZEOF
   *REDIR
   *ANSIALIAS
   *DIG
RAPH
   *NOROCONST
   *ROSTRIN
   *TUNE(8)
   *ARCH(8)
   *SPILL(128)
   *MAXMEM(2097152)
   *NOCOMPACT
   *TARGET(LE,CURRENT)
   *FLAG(I)
   *NOTEST(SYM,BLOCK,LINE,PATH,HOOK)
   *NOOPTIM
   *NOINLINE(AUTO,NOREPORT,100,1000)
   *NESTINC(255)
   *BITFIELD(UNSIGNED)
   *NOINFO
   *NODFP
   *NOVECTOR
   *FLOAT(HEX,FOLD,NO
MAF,AFP(NOVOLATILE))
   *STRICT
   *NOCOMPRES
   *NOSTRICT_INDUCTION
   *AGGRCOPY(NOOVERLAP)
   *CHARS(UNSIGNED)
   *NOIGNERR
NO
   *NOINI
TAUTO
   *CSECT(CONVERT2)
   *NOEVENTS
   *ASSERT(RESTRICT)
   *NORESTRICT
   *OBJECT
   *NOGENASM
   *OPTFILE(DD:OPTFILE)
   *NOSERVICE
   *NOOE
   *NOIPA
   *SEARCH(//'CEE.SCEEH.+')
   *NOLSEARCH
   *NOLOCALE
   *HALT(16)
   *PLIST(HOST)
   *NOCONVLIT
   *NOASCII
   *GOFF
   *ILP32
   *NOWARN64
   *NOHGPR
   *NOHOT
   *NOMETAL
   *NOARMOD
   *NOXPLINK(NOBACKCHAIN,NOSTOREARGS,NOCALLBACK,GUARD,OSCALL(NOSTACK))
   *ENUMSIZE(SMALL)
   *NOHALTONMSG
   *NOSUPPRESS
   *NORTCHECK
   *NODEBUG
   *NOSQL
   *NOCICS
   *UNROLL(AUTO)
   *KEYWORD()
   *NOKEYWORD(asm,typeof)
   *NOSEVERITY
   *NODSAUSER
   *NOINCLUDE
   *NOSMP
   *SYSSTATE(NOASCENV,OSREL(NONE))
   *NOFUNCEVENT
   *NOASM
   *NOASMLIB

   DEFINE(HAVE_CONFIGH=1)
   DEFINE(HAVE_STDINT_H=1)
   DEFINE(_XOPEN_SOURCE=1)
   DEFINE(_POSIX_SOURCE=1)
   UNDEFINE(__cplusplus)
   DEFINE(PCRE2_CODE_UNIT_WIDTH=8)
   DEFINE(NATIVE_ZOS=1)
   DEFINE(EBCDIC=1)
   UNDEFINE(SUPPORT_JIT)
   UNDEFINE(NATIVE_ZOS_POSIX)
  


The linkage step looks like:
XX*--
XX* LINKEDIT STEP:
XX*--
IEFC653I SUBSTITUTION JCL - UNIT=SYSALLDA,SPACE=(32000,(30,30)),DCB=(
   //USERLIB  DD DSN=,DISP=SHR
   IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.SRCE,DISP=SHR
   //COMPILE.SYSCRPT DD SYSOUT=*
   //OPTFILE DD DSN=(OPTFILE),DISP=SHR
   IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.JCLLIB(OPTFILE),DISP=SHR
   XXLKED   EXEC PGM=HEWL,COND=(4,LT,COMPILE),REGION=,PARM=''
IEFC653I SUBSTITUTION JCL - PGM=HEWL,COND=(4,LT,COMPILE),REGION=1024K
   //LKED.SYSLIB  DD
   X/SYSLIB   DD  DSNAME=,DISP=SHR
   IEFC653I SUBSTITUTION JCL - DSNAME=CEE.SCEELKED,DISP=SHR
   //DD DSN=,DISP=SHR
   IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.LOADLIB,DISP=SHR
   XXSYSPRINT DD  SYSOUT=*
   XXSYSLIN   DD DSNAME=*.COMPILE.SYSLIN,DISP=(OLD,DELETE)
   ZZ DD  DDNAME=SYSIN
   XXSYSLMOD  DD  DSNAME=
   IEFC653I SUBSTITUTION JCL - DSNAME=&(GO),DISP=(MOD,PASS),SPACE=(XXSYSUT1
   DD  UNIT=,SPACE=
   IEFC653I SUBSTITUTION JCL - UNIT=SYSALLDA,SPACE=(32000,(30,30))
   //SYSIN DD DSN=(),DISP=SHR
IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.CNTLLIB(CONVERT2),DISP=SHR
   X/SYSINDD  DUMMY
  
  
  with a bunch of include statements:


   BATCH EMULATOR  JOB(ZATLAS1C) STEP(STEP16  ) PGM=
   HEWL  PROCEDURE(LKED)
   IEW2278I B352 INVOCATION PARAMETERS -
   AMODE=31,MAP IEW2322I 1220  1INCLUDE
   SYSLIB(STRINGU2)   IEW2322I
   1220  2INCLUDE
   SYSLIB(CONTEXT2)
   IEW2606S 4B39 MODULE INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND 
CANNOT
  


Ze'ev Atlas
  


--

Re: I am getting IEW2606S in HEWL despite the fact that the target library IS PDSE

2017-09-03 Thread Lizette Koehler 
I tried to reformat this so it is easier to read.  One thing I do is place a 
couple of blanks at the beginning of the line when I have a list I am 
producing.  It sometimes help to keep the lines individual rather than mashed 
together.

Let me know if I incorrectly formatted the Options or LKED JCL.

Thanks

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Ze'ev Atlas
> Sent: Sunday, September 03, 2017 8:34 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: I am getting IEW2606S in HEWL despite the fact that the target
> library IS PDSE
> 
> Hi allI am compiling and linking a bunch of C programs using ZOS V2.2 z/OS XL
> C and z/OS V2 R2 BINDER.  Most compile and link without any issue despite the
> fact that I have and use longnames.  I am getting IEW2606S in HEWL for three
> of these programs despite the fact that the target library IS PDSE.  Please
> see if you have any clue why would that happen IEW2606S 4B39 MODULE
> INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND CANNOT BE SAVED IN LOAD
> MODULE FORMAT.
> 
 I use the same options for all the programs.
   Compile options:
  *NOGONUMBER
  *NOALIAS
  *NORENT 
  *TERMINAL   
  *NOUPCONV   
  *SOURCE 
  *NOLIST 
  *NOXREF
  *NOAGG  
  *NOPPONLY   
  *NOEXPMAC   
  *NOSHOWINC  
  *NOOFFSET   
  *MEMORY 
  *S
   SCOMM 
  *NOSHOWMACROS   
  *SKIPSRC(SHOW)  
  *NOREPORT   
  *NOMAKEDEP
  *PREFETCH   
  *THREADED
  *LONGNAME   
  *START  
  *EXECOPS
  *ARGPARSE   
  *NOEXPO
   RTALL
  *NODLL(NOCALLBACKANY
  *NOLIBANSI  
  *NOWSIZEOF  
  *REDIR  
  *ANSIALIAS  
  *DIG
   RAPH
  *NOROCONST  
  *ROSTRIN
  *TUNE(8)
  *ARCH(8)
  *SPILL(128)
  *MAXMEM(2097152)
  *NOCOMPACT  
  *TARGET(LE,CURRENT) 
  *FLAG(I) 
  *NOTEST(SYM,BLOCK,LINE,PATH,HOOK)   
  *NOOPTIM
  *NOINLINE(AUTO,NOREPORT,100,1000)   
  *NESTINC(255)   
  *BITFIELD(UNSIGNED) 
  *NOINFO   
  *NODFP  
  *NOVECTOR   
  *FLOAT(HEX,FOLD,NO
   MAF,AFP(NOVOLATILE))  
  *STRICT  
  *NOCOMPRES
  *NOSTRICT_INDUCTION 
  *AGGRCOPY(NOOVERLAP)
  *CHARS(UNSIGNED)
  *NOIGNERR
   NO 
  *NOINI
   TAUTO 
  *CSECT(CONVERT2)
  *NOEVENTS
  *ASSERT(RESTRICT)  
  *NORESTRICT 
  *OBJECT  
  *NOGENASM 
  *OPTFILE(DD:OPTFILE)  
  *NOSERVICE  
  *NOOE 
  *NOIPA   
  *SEARCH(//'CEE.SCEEH.+')
  *NOLSEARCH 
  *NOLOCALE   
  *HALT(16)   
  *PLIST(HOST) 
  *NOCONVLIT
  *NOASCII
  *GOFF   
  *ILP32  
  *NOWARN64
  *NOHGPR 
  *NOHOT  
  *NOMETAL
  *NOARMOD
  *NOXPLINK(NOBACKCHAIN,NOSTOREARGS,NOCALLBACK,GUARD,OSCALL(NOSTACK))   
  
  *ENUMSIZE(SMALL)   
  *NOHALTONMSG 
  *NOSUPPRESS
  *NORTCHECK 
  *NODEBUG   
  *NOSQL   
  *NOCICS   
  *UNROLL(AUTO) 
  *KEYWORD()
  *NOKEYWORD(asm,typeof)
  *NOSEVERITY
  *NODSAUSER
  *NOINCLUDE
  *NOSMP
  *SYSSTATE(NOASCENV,OSREL(NONE))   
  *NOFUNCEVENT  
  *NOASM
  *NOASMLIB

  DEFINE(HAVE_CONFIGH=1)  
  DEFINE(HAVE_STDINT_H=1)  
  DEFINE(_XOPEN_SOURCE=1)
  DEFINE(_POSIX_SOURCE=1)   
  UNDEFINE(__cplusplus)
  DEFINE(PCRE2_CODE_UNIT_WIDTH=8)   
  DEFINE(NATIVE_ZOS=1)
  DEFINE(EBCDIC=1)  
  UNDEFINE(SUPPORT_JIT)
  UNDEFINE(NATIVE_ZOS_POSIX) 
 

The linkage step looks like:
   XX*--
   XX* LINKEDIT STEP:   
   XX*-- 
   IEFC653I SUBSTITUTION JCL - UNIT=SYSALLDA,SPACE=(32000,(30,30)),DCB=(
  //USERLIB  DD DSN=,DISP=SHR  
  IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.SRCE,DISP=SHR  
  //COMPILE.SYSCRPT DD SYSOUT=*
  //OPTFILE DD DSN=(OPTFILE),DISP=SHR  
  IEFC653I SUBSTITUTION JCL - DSN=ZATLAS1.PCRE2.JCLLIB(OPTFILE),DISP=SHR
  XXLKED   EXEC

I am getting IEW2606S in HEWL despite the fact that the target library IS PDSE

2017-09-03 Thread Ze'ev Atlas 
Hi allI am compiling and linking a bunch of C programs using ZOS V2.2 z/OS XL C 
and z/OS V2 R2 BINDER.  Most compile and link without any issue despite the 
fact that I have and use longnames.  I am getting IEW2606S in HEWL for three of 
these programs despite the fact that the target library IS PDSE.  Please see if 
you have any clue why would that happen IEW2606S 4B39 MODULE INCORPORATES 
VERSION 3 PROGRAM OBJECT FEATURES AND CANNOT BE SAVED IN LOAD MODULE FORMAT. 

I use the same options for all the programs.
Compile options:
*NOGONUMBER *NOALIAS    *NORENT     *TERMINAL   *NOUPCONV   *SOURCE     *NOLIST 
*NOXREF     *NOAGG      *NOPPONLY   *NOEXPMAC   *NOSHOWINC  *NOOFFSET   *MEMORY 
    *SSCOMM *NOSHOWMACROS           *SKIPSRC(SHOW)          *NOREPORT   
*NOMAKEDEP  *PREFETCH   *THREADED*LONGNAME   *START      *EXECOPS    *ARGPARSE  
 *NOEXPORTALL*NODLL(NOCALLBACKANY*NOLIBANSI  *NOWSIZEOF  *REDIR      *ANSIALIAS 
 *DIGRAPH    *NOROCONST  *ROSTRIN*TUNE(8)    *ARCH(8)    *SPILL(128) 
*MAXMEM(2097152)        *NOCOMPACT          *TARGET(LE,CURRENT)     *FLAG(I)    
*NOTEST(SYM,BLOCK,LINE,PATH,HOOK)   *NOOPTIM*NOINLINE(AUTO,NOREPORT,100,1000)   
*NESTINC(255)           *BITFIELD(UNSIGNED) *NOINFO                             
                                            *NODFP                              
                                            *NOVECTOR                           
                                            
*FLOAT(HEX,FOLD,NOMAF,AFP(NOVOLATILE))                                          
*STRICT                                                                         
*NOCOMPRESS *NOSTRICT_INDUCTION     *AGGRCOPY(NOOVERLAP)    *CHARS(UNSIGNED)    
*NOIGNERRNO                                                                     
*NOINITAUTO                                                                     
*CSECT(CONVERT2)                                                                
*NOEVENTS                                                                       
*ASSERT(RESTRICT)                                                               
*NORESTRICT                                                                     
*OBJECT                                                                         
*NOGENASM                                                                       
*OPTFILE(DD:OPTFILE)                                                            
*NOSERVICE                                                                      
*NOOE                                                                           
*NOIPA                                                                          
*SEARCH(//'CEE.SCEEH.+')                                                        
*NOLSEARCH                                                                      
*NOLOCALE   *HALT(16)   *PLIST(HOST)                                            
*NOCONVLIT                                                                      
*NOASCII                                                                        
*GOFF       *ILP32      *NOWARN64   *NOHGPR     *NOHOT      *NOMETAL    
*NOARMOD*NOXPLINK(NOBACKCHAIN,NOSTOREARGS,NOCALLBACK,GUARD,OSCALL(NOSTACK))     
        *ENUMSIZE(SMALL)                                                        
        *NOHALTONMSG                                                            
        *NOSUPPRESS                                                             
        *NORTCHECK                                                              
        *NODEBUG                                                                
        *NOSQL                                                                  
        *NOCICS                               *UNROLL(AUTO)                     
    *KEYWORD()                            *NOKEYWORD(asm,typeof)                
*NOSEVERITY                           *NODSAUSER                            
*NOINCLUDE                            *NOSMP                                
*SYSSTATE(NOASCENV,OSREL(NONE))       *NOFUNCEVENT                          
*NOASM                                *NOASMLIB                             
DEFINE(HAVE_CONFIG_H=1)  DEFINE(HAVE_STDINT_H=1)               
DEFINE(_XOPEN_SOURCE=1)               DEFINE(_POSIX_SOURCE=1)               
UNDEFINE(__cplusplus)                 DEFINE(PCRE2_CODE_UNIT_WIDTH=8)       
DEFINE(NATIVE_ZOS=1)                  DEFINE(EBCDIC=1)                      
UNDEFINE(SUPPORT_JIT)                 UNDEFINE(NATIVE_ZOS_POSIX)    
The linkage step looks like:
XX*--XX* 
LINKEDIT STEP:                                                   
XX*--IEFC653I 
SUBSTITUTION JCL - UNIT=SYSALLDA,SPACE=(32000,(30,30)),DCB=(//USERLIB  DD 
DSN=,DISP=SHR              IEFC653I SUBSTITUTION 
JCL - DSN=ZATLAS1.PCRE2.SRCE,DISP=SHR          //COMPILE.SYSCRPT DD SYSOUT=*  

zFS Growth and effect on applications in z/OS

2017-09-03 Thread Lizette Koehler 
Need some guidance here

I have created a V5 zFS file that has EA/EF. The primary allocation is 2000
cylinders and the secondary is 5000 cylinders. 

The application expects this file to grow to over 1TB in size. 

An application using the zFS gets messages indicating the file is full.  But
from a LISTC it is not - it is 5GB in size and using 3GB


09:51:37 03SEP PR01 IOEZ00312I Dynamic growth of aggregate OMVS.MY.ZFS in
progress, (by user X 

09:51:38 03SEP PR01 IOEZ00309I Aggregate OMVS.MY.ZFS. ZFS successfully
dynamically grown (by user X 
09:51:38 03SEP PR01 IOEZ00078E zFS aggregate OMVS.MY.ZFS exceeds 95% full
(388000/391200) (WARNIN 
 
3,178,496,000/3,204,710,400 

I am not seeing an 2C3 abends (so far), I do not see any BPX messages (so far)


The Hi-U-RBA from LISTC matches the numbers in the IOEZ00078E message. 

I checked throughout the day, the file seems to get a lot of the following
messages 

 IOEZ00312I 
 IOEZ00309I 
 IOEZ00078E 

So I am not sure why the zfs full is occurring. 

   1) what is the impact of dynamic growth on zFS users? 
 a) Does it cause an application to fail during growth 
 b) are there other "cache" things in zFS I should be looking at?
   2) What other cache could impact a zFS application 
  a) the V5 zFS file I created is at 5GB in size - I coded it with EXTENDED
EXT-ADDR ZFS 
   3) What diagnostics can I use to determine why this application is having
issues?

Any thoughts or suggestions appreciated.  I am just not seeing a solution

Thanks


Lizette Koehler
statistics: A precise and logical method for stating a half-truth inaccurately

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

errno JRPswKeyNtValid from BPX1MSS while using EZASMI sockets

2017-09-03 Thread Joseph Reichman 
Hi

 

I have started task which I originally tested out under TESTAUTH (making
allowances that I was running under TEST)

 

Anyway this program via EZASMI interface communicates with windows Np. I get
a call to download something to the Windows FTP interface

 

There is a sample code that I copied and modified using EZAFTPKS program
interface. Before the first call to EZAFTPKS there is a call to BPX1MSS

 

This worked under TEST now while running as a started task BPX2MSS fail
return code 9C errno JRPswKeyNotValid. X'0200"

 

 

Doing research seems like my EZASMI INIT call already identified the task to
OMVS and while googling I saw apar that EZASMI did this with PSW key 6 

 

Would I have to do SPKA 6 to get things going ?

 

My program does get in and out SUPERVISOR STATE and Key 0  at times but in
the call to BPX1MSS its under key 8

 

 

Can anybody shed some light on this?   

 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: WinSCP or FileZilla to z/OS (not OMVS) ?

2017-09-03 Thread Roger Bolan 
Not for me.  The Remote Site says 'BOLAN.' for MVS, and /u/bolan for OMVS.
I have two different site definitions in the Filezilla site manager.  I
tried swapping on the Remote Site screen and it gets errors if I try to use
an OMVS HFS directory on the site that uses 'BOLAN.' and vice versa.  I am
not using SFTP just FTP and passive mode.  I also do not use anonymous
logon but have to give a userid and password for both sides.  When I do
this from outside my office there are some additional VPN and firewall
logins I need before I can use Filezilla for anything, but I imagine that
is not Lionel's problem because he said he could get to the OMVS side.

On Sat, Sep 2, 2017 at 3:00 PM, Wayne Bickerdike  wrote:

> I use Filezilla.
>
> Thought it was just wrap quotes around the dataset name for z/OS otherwise
> it goes to a USS file.
>
> On Sat, Sep 2, 2017 at 7:42 AM, Paul Gilmartin <
> 000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
> > On Fri, 1 Sep 2017 13:42:00 -0600, Roger Bolan wrote:
> >
> > >I use Filezilla to connect to my z/OS systems both for MVS datasets and
> > >OMVS.  I have the same IP address for both site definitions.  As far as
> I
> > >can tell the only difference is on the Advanced Tab in the Site Manager
> > >where the OMVS site definition has a default remote directory of
> /u/bolan
> > >defined, and the MVS site definition has a blank default remote
> directory.
> > >
> > Does FileZilla support both FTP and sftp?  Is it possible, then, that
> your
> > success was with Classic FTP and the OP's failure was with sftp?
> >
> > Does configuring the Co:z server for sftp require admin privilege/
> >
> > >On Fri, Sep 1, 2017 at 12:14 PM, Dyck, Lionel B. (TRA) wrote:
> > >
> > >> Any thoughts on how to get WinSCP or FileZilla to access z/OS datasets
> > >> when  connected?
> > >>
> > >> All I am able to get is access to the OMVS side of the system.
> > >>
> > Life would be a lot simpler if people avoided Classic data sets.
> >
> > -- gil
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
>
>
>
> --
> Wayne V. Bickerdike
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN