s.
Could you please contact me off list to discuss further.
Would John McKown also like to contact me, your dabbling with Yacc and Perl
may mean you would enjoy this stuff.
Thanks
--
Julian Levens
--
For IBM-MAIN subscribe / sign
Joshua
I've solved this locally by arranging for the first PROC in my startup (well
before JES2) to run an IEBCOPY which copies all the parms in the appropriate
concatenation into a single PDSE as follows:
//LPARM PROC
//LPARM EXEC PGM=IEBCOPY,TIME=10
//P1DD DISP=SHR,DSN=CAP.&SYSLIB1.
As has been suggested earlier, you can place DLLs into PDSEs - I have done
this. There may be structural differences, one DLL becomes one PDSE
containing many seperate program objects (one PDSE = one DLL). I have never
created DLLs under USS, so I do not know exactly how they are organised here
exc
Hmmm
In the past when managing COBOL build options and Xpediter. We decided not
to optimise at all. We were not having performance problems (any we did were
to do with DB2/SQL within the programs), hence optimisation was deemed
unnecessary. This decision made code management much easier and allowe
All
> Shmuel Metz wrote:
>
> In <[EMAIL PROTECTED]>, on 12/05/2005
>at 08:49 AM, Daniel Cremieux <[EMAIL PROTECTED]> said:
>
> >I am converting a rexx program to cobol and having this problem . The
> >data is , for example x'0123' and after conversion , it must have
> >the value 123 (decimal
Dave
We had one fail and we simply asked IBM to replace it - about 3k GBP (thats
inc labour) as I recall. The drive itself is basically a fairly standard
SCSI drive encased in some IBM specific stuff. Its also part of a RAID array
and I believe the replacment needs to match the others in the array
Mark
> Ahhh... forgot about that feature. You don't need to create a
> separate data set though. Just use ZDEFAULT as the profile name
Of course, I should have realised that.
Ta, muchly
Julian
> on ISPF option 2 EDIT panel. This only needs to be done once (per
> profile data set - in case y
> On Mon, 24 Oct 2005 10:15:29 -0400, Robert A. Rosenberg
> <[EMAIL PROTECTED]>
> wrote:
>
> >At 09:44 -0500 on 10/18/2005, Mark Zelden wrote about Re: PREVENTING
> >TAKING TOO MUCH STOR IN ISPF:
> >
> >>Only one reason for me. Edit macros. Some of mine destroy/change
> >>data and it is a good h
All
I need to port our latest piece of software to the mainframe. The software
runs as a server using TCP/IP on Linux/Unix/Windows already. Therefore,
porting to USS should be fairly painless. What pros and cons would there be
porting this server to native z/OS?
+ Better performance?
+ Woul
Brian
RACF provides functionality in this area, password RULES or somesuch. See
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ichza720/5.2.1?AC
TION=MATCHES&REQUEST=password+rules&TYPE=FUZZY&SHELF=&DT=20020109124747&CASE
=&searchTopic=TOPIC&searchText=TEXT&searchIndex=INDEX&rank=RANK
Back in 1997 I finally managed to convince the powers that be where I worked
at that time, to instigate a new JCL standard. This consisted of using JOBs
that looked something like this.
//PAA123 JOB (ACC),'A JOB',CLASS=C,MSGCLASS=S
//*
//JCLLIB ORDER=(HLQ.PROD.PROCLIB)
//*
//INCLU
Don
> You wrote
> Your emulator must be translating incorrectly. The 'not' char is:
>
> B,
>
> which in ascii is: x'AC'
Its hard to be sure, but in Word (Windows?) it appears to be x'8c'
> and in ebcdic is: x'5F'
With my emulator ^ is x'5f'. I am using codepage 1047 which is useful for
working
>
> I quickly tested a little program.
>
> say \1
> say ^1
> say ?1
This last line was sent with the IBM 'not' character and returned as a
question mark! Enough said!
>
> On my set-up the first two returned 0 and the last one failed
> (invalid char
> in prog). However, in your case the second one
I quickly tested a little program.
say \1
say ^1
say ?1
On my set-up the first two returned 0 and the last one failed (invalid char
in prog). However, in your case the second one failed. This is related to
translation and codepage issues.
Therefore, I have in recent times been in the habit of us
Peter
As you say the manuals are not very clear. I struggled for a long time to
use IRXEXCOM, the problem was that parameters 2 and 3 have to point to the
same address (even though not used). I was passing 0 (zero) for both of
them, after all thats the same address. However, as you say the compile
Wang
I suspect you are compiling in C when you need to compile as C++. iostream.h
is a C++ library component.
HTH
Julian
>
> Hi all,
>
> I tried to use the head file iostream.h(in pds cbc.sclbh.h),but got
> error when compiled the source:
> (IOSTREAM):101 Definition of function class requi
We are running at CICS TS 2.2 and I could not find a way to make it work.
Eventually I found some appropriate documentation which suggested it wasn't
possible. I subsequently found a reference (I think via this list or the
CICS-List) talking about new features in CICS TS 3.1, which included DLL
sup
Bob
The short answer is yes. I recently found out that it is not possible under
CICS (until CICS TS 3.1 only just released).
It can become invloved if you wish your COBOL program to be called
dynamically and that program to call DLLs, but it's not that hard to sort
out.
HTH
Julian
> Help. Our
Larry
A return code 8 from BLDL means:
"A permanent I/O error was detected when the system attempted to search
the directory."
However, in my experience this sort of error can sometimes be misleading.
However, it should be a clue.
HTH
Julian
>
> Anybody have a similar problem when issuing
19 matches
Mail list logo
