I took out all the SYSLIB besides BND2
I added SCEERUN for DEBUG TOOL
While we are on the subject I was told that I can only invoke Debug tool from
EXEC PGM=EQANMFBG
Not by calling CEETEST in amode64 would you know anything about that
thanks
-Original Message-
From: IBM Mainframe
I'm not sure how you made the leap to the DLL module was not found. These
messages imply the CELQV003 was found but the xplink attribute did not match.
The binder uses the DLL module to validate attributes are correct instead of
doing this validation at run time.
I agree with Don that you
This is my compile JCL
>From preprocessor to compile to link/bind
preprocessor
your edit profile using the command RECOVERY ON.
//IBMUSER$ JOB 'ADCD V2R9','SYSPROG',NOTIFY=,REGION=0M
//*
That all looks as though you're mixing 31-bit and 64-bit objects. Was SYSADATA
compiled with the LP64 and DLL options?
In article <006901d561e6$72682d60$57388820$@gmail.com> you wrote:
> These are the error messages or some of them honestly I just went thru every
> CBC a CEE library and cannt
I see fopen in this DLL
ROWSECBC.SCLBDLL2(IOSX64) Li CHARS 'fopen'
found
ommand ===> Scroll ===>
PAGE
d_put__EI7ostreamFc..cout..dbp__EI9streambufFv..dec__Fli..dec__FR3ios..detac
h_
These are the error messages or some of them honestly I just went thru every
CBC a CEE library and cannt find CELQV003
IEW2322I 1220 8934IMPORT CODE64,'IOSX64','WS__FR7istream'
IEW2469E 9907 THE ATTRIBUTES OF A
I still don't see an error message. There is no DLL CELQV003. The import
statement just tells the binder how to link the program to find the
executable at run time. If you do a search inside CEE.SCEEBND2, you will
find eyecatchers for fopen (and other library routines). The run-time
code is going
You've missed the point. We need real details. For instance, the error message
should always be included instead of your interpretation of the message.
You could look in SMP/E and find out where CELQV003 is located. Maybe you are
missing the library.
Jon.
On Monday, September 2, 2019,
The syslin which the following IMPORT cann't find the DLL CELQV003
BROWSECEE.SCEELIB(CELQS003)
Command ===>
IMPORT CODE64,CELQV003,'FFLUSH',068
IMPORT CODE64,CELQV003,'fopen',069
I have the following SYSLIB
I'm sure the compiler has deficiencies. You're previous error program
showed one. While it would be nice to claim to be able to catch every
possible coding error, that's just not realistic. A "huge" number of
them? That would be news to us. We've been using this compiler/library
for many years
Yeah, things are so tiny these days have to take complete inventory of packing
list. I had three Info-32's and two worked out of the box. The third wouldn't
motor. The little IPDS card had been discarded with the wrapper.
First PSI is ping the IP address of printer and then LPR a test page.In a
On Sunday, September 1, 2019, 08:31:39 PM PDT, Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>> As for IBM C having several deficiencies, remember that z/OS is a
>> very complex OS compared to Unix where 1 size fits all.
> Simpler is better.
I never said
Have you tried contacting the vendor for assistance?
Since the type of printer can make things a challenge, you probably could get
better assistance from the vendor.
Remember - the less details provided - the less helpful answers you will get.
Its broke will not help you get answers
How it is
[Default] On 1 Sep 2019 20:31:40 -0700, in bit.listserv.ibm-main
000433f07816-dmarc-requ...@listserv.ua.edu (Paul Gilmartin) wrote:
>On Mon, 2 Sep 2019 02:39:26 +, Jon Perryman wrote:
>
>> There are 2 PTF's listed in the apar
>>
Jon
Just on the phone with IBM the date of the fix nov 2, 2016 was for 2.1 , 2.2
They said should have been resolved for 2.3
They said level 2 will get back to me
Tommorow
Thanks
> On Sep 1, 2019, at 10:39 PM, Jon Perryman wrote:
>
> There are 2 PTF's listed in the apar
>
Does it have a whole lot of at @ symbols? Those are blanks in EBCDIC.
On Mon, Sep 2, 2019 at 1:36 AM Jake Anderson wrote:
>
> Hi
>
> Cross posted
>
> We have installed a new printer from hardware side . I have done all the
> mainframe part of adding the printer definitions.
>
> The problem is
Is it OK to use the stool that came with a z890 to repair a z13s?
The ladder that came with the z13s has gone missing.
Gadi
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
I am pleased to invite you to a GSE Large Systems Working Group event. The
event will be a virtual event via WebEx on the 25th September 2019 from 13:30 –
15:45 BST.
The event will contain 2 sessions presented by Anna Shugol from IBM and Jeanne
Glass from Virtual z Computing.
* IBM
I am pleased to invite you to a GSE Large Systems Working Group event. The
event will be a virtual event via WebEx on the 25th July 2019 from 13:30 –
15:45 BST.
The event will contain 2 sessions presented by Anna Shugol from IBM and Jeanne
Glass from Virtual z Computing.
* IBM Update
*
Hi
Cross posted
We have installed a new printer from hardware side . I have done all the
mainframe part of adding the printer definitions.
The problem is when they initiate a print from Mainframe it gives a
unreadable format while printing out .
Is it something within the printer has to be set
20 matches
Mail list logo
