Re: OT: Happy New Year!

2014-09-24 Thread John Weber
I couldn't agree more.   NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. All

Re: Sorry state of IT education?

2014-04-22 Thread John Weber
This is why common core standards are igniting education. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: Tuesday, April 22, 2014 5:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Sorry state of IT education? Not

Re: Another Golden Anniversary - Dartmouth BASIC

2014-04-09 Thread John Weber
Basic on a Commodore 64 as a hobby. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Wednesday, April 09, 2014 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Another Golden Anniversary - Dartmouth BASIC OK, not a big

VSAM Status Code 16/24 on READPREV

2013-08-01 Thread John Weber
All, We are receiving a status code 16/24 while performing a KSDS VSAM 'READPREV'. This exception only occurs when the key is specified but does not occur if it is not entered through our UI. References point to it having MicroFocus origins, but we are running this on the mainframe under

Re: VSAM Status Code 16/24 on READPREV

2013-08-01 Thread John Weber
to SYSLOG at the time of the error, you might find some additional messages (IEC or other) Also, the CICS log may help. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Weber Sent: Thursday, August 01, 2013 8:26 AM To: IBM

Re: VSAM Status Code 16/24 on READPREV

2013-08-01 Thread John Weber
: Thursday, August 01, 2013 8:52 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: VSAM Status Code 16/24 on READPREV On Thu, 1 Aug 2013 15:25:55 +, John Weber wrote: All, We are receiving a status code 16/24 while performing a KSDS VSAM 'READPREV'. This exception only occurs when the key

Re: VSAM Return Code 44 Received on Write to Fixed Length File

2012-11-21 Thread John Weber
. Or on an EXAMINE on it. On Nov 19, 2012 6:52 PM, John Weber j...@fiteq.com wrote: Interesting about a secondary status variable. We'll investigate that. Regarding the AIX definitions. We do not include a RECORDSIZE parameter. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM

VSAM Return Code 44 Received on Write to Fixed Length File

2012-11-19 Thread John Weber
We are using a batch process to write account records to a VSAM file while also writing records to an audit file which is also a VSAM file. Both files include an index and several alternate indexes. Each alternate index allows duplicates (NONUNIQUEKEY). The audit file receives a VSAM return code

Re: VSAM Return Code 44 Received on Write to Fixed Length File

2012-11-19 Thread John Weber
Code 44 Received on Write to Fixed Length File Could you post the IDC messages for the 44? Lizette -Original Message- From: John Weber j...@fiteq.com Sent: Nov 19, 2012 4:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: VSAM Return Code 44 Received on Write to Fixed Length File We are using

Re: VSAM Return Code 44 Received on Write to Fixed Length File

2012-11-19 Thread John Weber
comes to mind in your case is that the RECORDSIZE on your AIX is too small to record all the base keys associated with a single AIX key. This can cause a 44. Normally these keys are either ALL SPACES or ALL LOW-VALUES or maybe ALL HIGH-VALUES. On Nov 19, 2012 6:21 PM, John Weber j...@fiteq.com

Re: VSAM Return Code 44 Received on Write to Fixed Length File

2012-11-19 Thread John Weber
To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: VSAM Return Code 44 Received on Write to Fixed Length File Then u get some default. Do a LISTC on the AIX to see what it is. You might want to PRINT the records in the AIX itself just to see. Or on an EXAMINE on it. On Nov 19, 2012 6:52 PM, John Weber j

Re: COBOL Compiler Question

2012-10-19 Thread John Weber
COBOL Development and Performance On Fri, 12 Oct 2012 23:21:59 +, John Weber j...@fiteq.com wrote: We have a COBOL CICS module being called using the LINK command. Here is the interface call: EXEC CICS LINK PROGRAM('PROGRAM1') RESP(WS-RESP

Re: COBOL Compiler Question

2012-10-19 Thread John Weber
?  If that is the case then I can't say for sure.  I bet it is still possible, but I couldn't say for sure how it could be done. Frank From: John Weber j...@fiteq.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, October 19, 2012 8:28 AM Subject: Re: COBOL Compiler Question Thank

Re: COBOL Compiler Question

2012-10-19 Thread John Weber
initialization.  All it does is it applies the VALUE clause to each associated working-storage field each time that your COBOL subroutine is called, rather than only the first time it is called. Frank From: John Weber j...@fiteq.com To: IBM-MAIN@LISTSERV.UA.EDU

Re: COBOL Compiler Question

2012-10-16 Thread John Weber
that require it. I would guess that options 3 (LOCAL STORAGE) or 4 (explicit initialization) would give you the best performance. Have I forgotten anything? Possibly. Have fun! Frank From: John Weber j...@fiteq.com To: IBM-MAIN@LISTSERV.UA.EDU Sent

COBOL Compiler Question

2012-10-12 Thread John Weber
We have a COBOL CICS module being called using the LINK command. Here is the interface call: EXEC CICS LINK PROGRAM('PROGRAM1') RESP(WS-RESP) COMMAREA(WS-COMMAREA) END-EXEC However, it has been brought up that creating a bound module instead of