Re: hexing and cursing

2014-11-06 Thread Elardus Engelbrecht
Ed Finnell wrote: What was it the 'Basic screw' to enable the language? Aw, screw it, the basic answer is 'Basic' language!!! [ pun intended :-D ] Sorry and sorry, but I just can't resist. And cannot wait for Friday. Ok, I'll hide under my rock. Groete / Greetings Elardus Engelbrecht

IEAMDBLG. Filter by SYSNAME

2014-11-06 Thread Jorge Garcia
Hello: We are going to customize IEAMDBLG program for extract records from OPERLOG. We've reviewed the parameters and there isn't any parm for filter for SYSID or SYSNAME. Is there any option for execute it with this option? Regards Jorge Garcia Juanino Gerente sistemas z/OS ACTP – DIAC –

Re: IEAMDBLG. Filter by SYSNAME

2014-11-06 Thread Anthony Thompson
You'll need to modify the assembler source for IEAMDBLG in SYS1.SAMPLIB to provide for that functionality. That's what I did. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jorge Garcia Sent: Thursday, 6 November 2014 6:58 PM

Re: Exposing USS Messages to z/OS SYSLOG

2014-11-06 Thread Jousma, David
Kees, Its working on my 1.13 system. Not sure if you just had a typo with /dev/syslog. Its /dev/console or /dev/operlog for operlog you have to add 1 byte to the front of the message though: The following are system console files: /dev/console (major 9, minor 0). Data written to the

Re: System vs. user ABEND codes

2014-11-06 Thread Shmuel Metz (Seymour J.)
In 5544467947344337.wa.paulgboulderaim@listserv.ua.edu, on 11/04/2014 at 05:47 PM, Paul Gilmartin 000433f07816-dmarc-requ...@listserv.ua.edu said: In a CDC operating system, octal ruled. And in another it didn't. Don't even think about octal K (512). -- Shmuel (Seymour J.)

Help understanding a zFS error

2014-11-06 Thread Lizette Koehler
We are z/OS V1.12 heading to V2.1 On one of my LPARs I get the following message when I use ISHELL to allocate a new small zFS File (5cyls by 1 cyls). I did not even get a chance to format it as the zFS was deleted when I hit enter. Where would I find the ERRNO=84x? Errno=84x ENOMEM: Not

Re: Help understanding a zFS error

2014-11-06 Thread Schroeder, Wayne
Lizette, Here is what I found on IBM site. OA06260: USING THE ISHELL INTERFACE TO CREATE A NEW ZFS FAILS WITH ERRNO ENOMEM RSN EF176311 User attempting to use the ishell interface to 'create a new zfs' fails with Errno=84x ENOMEM: Not enough space is available. Reason=EF176311 The errno ENOMEM is

Re: IEAMDBLG. Filter by SYSNAME

2014-11-06 Thread Jorge Garcia
Anthony, Do you have any problem in send us your source program with the enhacement? Regards -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO

Re: Help understanding a zFS error

2014-11-06 Thread Lizette Koehler
Thanks, however that is not my Reason code. My reason code is EFE1670A. This APAR documents EF176311 Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Schroeder, Wayne Sent: Thursday, November 06, 2014 8:22 AM To:

Re: Help understanding a zFS error

2014-11-06 Thread Mike Schwab
Errno=84x ENOMEM: Not enough space is available. Reason=EFE1670Ax Description: Internal failure obtaining MEMORY for operation. Press Enter to continue. What is your current region for your userid? On Thu, Nov 6, 2014 at 9:12 AM, Lizette Koehler stars...@mindspring.com wrote: We are z/OS

Above the bar storage and CPOOL

2014-11-06 Thread Donald Likens
I am confused... It states in the Authorized Assembler Services Reference, Volume 1 (ALE-DYN) LOC=(RES,64) indicates that the location of virtual storage depends upon the location of the caller. If the caller resides below 16 megabytes, virtual storage is to be located below 16 megabytes; if

Re: Above the bar storage and CPOOL

2014-11-06 Thread Dave Day
Use IARCP64, not CPOOL On 11/6/2014 9:43 AM, Donald Likens wrote: I am confused... It states in the Authorized Assembler Services Reference, Volume 1 (ALE-DYN) LOC=(RES,64) indicates that the location of virtual storage depends upon the location of the caller. If the caller resides below 16

Re: Above the bar storage and CPOOL

2014-11-06 Thread Binyamin Dissen
On Thu, 6 Nov 2014 09:43:27 -0600 Donald Likens dlik...@infosecinc.com wrote: :I am confused... It states in the Authorized Assembler Services Reference, Volume 1 (ALE-DYN) :LOC=(RES,64) indicates that the location of virtual storage depends upon the location of the caller. If the caller

Re: Above the bar storage and CPOOL

2014-11-06 Thread Donald Likens
The problem with IARV64 is that the smallest amount of memory it will obtains is 1 meg. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Above the bar storage and CPOOL

2014-11-06 Thread Donald Likens
I think you must have us confused with another company because InfoSec Inc. tries very hard to keep its customers happy. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu

Re: Exposing USS Messages to z/OS SYSLOG

2014-11-06 Thread Hank Oerlemans
http://www-01.ibm.com/support/docview.wss?uid=swg1PM93967 refers to ras_message_routing_console and BBOO0221W Perhaps this is of use to you ? Hank -- For IBM-MAIN subscribe / signoff / archive access instructions, send

Re: Help understanding a zFS error

2014-11-06 Thread Lucas Rosalen
Maybe a too low ASSIZEMAX either defaulted or in user's OMVS segment could cause this (I'm in my phone, can't do a very good research though). Lucas Rosalen Em 06/11/2014 13:42, Mike Schwab mike.a.sch...@gmail.com escreveu: Errno=84x ENOMEM: Not enough space is available. Reason=EFE1670Ax

Re: Above the bar storage and CPOOL

2014-11-06 Thread Farley, Peter x23353
And that is why IARST64 and IARCP64 were introduced in z/OS V1.10. Allows managing 64-bit storage in chunks from 1-64K or pool sizes up to .5 Meg. From a current discussion on the ASSEMBLER list, this SHARE presentation is quite helpful: Take a look at this presentation:

Re: Help understanding a zFS error

2014-11-06 Thread Lizette Koehler
Thanks everyone I have 2gb tso size. I have the security I need. What it looks like are my page ds are too high. Going to try an ipl to see if it fixes it. I did set the IF Slip per IBM doc and it failed to take the svc dump with a message that states. Insufficient storage Lizette

Re: Help understanding a zFS error

2014-11-06 Thread Thomas Conley
On 11/6/2014 10:12 AM, Lizette Koehler wrote: We are z/OS V1.12 heading to V2.1 On one of my LPARs I get the following message when I use ISHELL to allocate a new small zFS File (5cyls by 1 cyls). I did not even get a chance to format it as the zFS was deleted when I hit enter. Where would I

Re: Help understanding a zFS error

2014-11-06 Thread Lizette Koehler
That is what I was thinking. Thanks for confirming that these messages are not well documented. Lizette -Original Message- From: Thomas Conley pinnc...@rochester.rr.com Sent: Nov 6, 2014 4:53 PM To: IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu Subject: Re: Help understanding

Re: IEAMDBLG. Filter by SYSNAME

2014-11-06 Thread Anthony Thompson
Sent off-list. Cheers, Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jorge Garcia Sent: Friday, 7 November 2014 12:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEAMDBLG. Filter by SYSNAME Anthony, Do you have any problem

Re: Above the bar storage and CPOOL

2014-11-06 Thread Jim Mulder
I am confused... It states in the Authorized Assembler Services Reference, Volume 1 (ALE-DYN) LOC=(RES,64) indicates that the location of virtual storage depends upon the location of the caller. If the caller resides below 16 megabytes, virtual storage is to be located below 16