Re: Debugging TSO FTP command

2008-04-08 Thread Hunkeler Peter (KIUK 3)
Thanks again John.  I added an OMVS segment to the group my userid is 
associated with and a GID(1) to the segment, and I now have access to 
FTP from the ISPF option 6 command line.

Just a word of caution here. It seems your environment has not been 
properly setup for z/OS UNIX: Your userid seems to have had an OMVS 
segment already but your default group didn't.

Usually GID(1) is assigned to group OMVSGRP (if the setup
recommendations 
are followed). I doubt your default group is OMVSGRP, so you just 
assigned GID(1) to a second group. Don't do this. GIDs as well as UIDs 
should *not* be shared between multiple groups and userids, resp. This 
will lead to troubles sooner or later.


Here is a useful link that is of great help in finding message and 
codes explanation:

http://www-03.ibm.com/systems/z/os/zos/bkserv/lookat/

Simply enter the message id or code in the Message Id field an hit 
enter. (Unfortunately, LookAt does not support BPXMTEXT reason codes).

-- 
Peter Hunkeler
Credit Suisse

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



Re: Debugging TSO FTP command

2008-04-08 Thread Chris Mason
Dave

This response is also taking into account other responses in this thread.

I'm glad you are now working mainly with help from John McKown.

I have just dealt with a very similar message-based issue, specifically 
relating 
to Language Environment codes, with a customer and also in the ibmtcp-l list. 
Let us review how you could have been more self-sufficient.

The starting point is what the system gave you: message CEE5101C.

As Peter Hunkeler pointed out, even if you know all of the component-
identifying letters, the easiest way to find your way to an explanation is the 
IBM LookAt! web page.

Thus, for CEE5101C, we find:

quote

1.513 CEE5101C

   CEE5101C During initialization, the callable service BPX1MSS failed. The
  system return code was return_code; the reason code was
  reason_code. The application will be terminated.

Explanation: The callable service BPX1MSS failed with return code return_code 
and reason code reason_code because the application was not authorized to 
use UNIX System Services.

Programmer Response: Contact your system administrator to have the id 
registered with UNIX System Services to use these services. See z/OS UNIX 
System Services Programming: Assembler Callable Services Reference for the 
appropriate action to take for this return code and reason code. Consult with 
your UNIX System Services support personnel if necessary.

System Action: The application is terminated.

Symbolic Feedback Code: CEE4VD

/quote

So I'd be inclined to say that the key was just finding the explanation of 
the 
message in the manual.

John McKown offered a short-cut based on having spotted an 8-character 
hexadecimal string in the message text. No doubt in his sleep he can now 
perform the trick of using BPXMTEXT in order to translate such a string into 
what the developer at least considers is English.

The labour-intensive alternative to using BPXMTEXT for the reason code text 
is simply to follow-up what the online version of the message offers and follow 
the link to the suggested manual.

I have to admit that there is a bit of stupidity here requiring a bit of 
confidence in following links.

The manual to which you are directed is z/OS UNIX System Services 
Programming: Assembler Callable Services Reference. This does not look quite 
so helpful at first glance. What you need to do is pluck up some courage and 
look for likely headings in the Contents. It is to be hoped that your eye 
quickly 
spots Return_Code and Reason_Code.

The nonsense is that you find yourself directed to yet another manual where 
the golden keys are to be found: z/OS UNIX System Services Messages and 
Codes in both cases, wouldn't you know?

You are now allowed, soto voce of course, to express your disgust at having 
so pointlessly to look up, albeit with the click of a mouse, two manuals when 
one would have sufficed.

The golden keys are:

return code was 000156

From 3.0 Return Codes (Errnos) Listed by Value

Decimal Value: 156
Hexadecimal Value: 9C
Return Code: EMVSINITIAL
Description: Process Initialization error.

 and

reason code was 0B0C00FA

From 4.2 Reason Codes

Value: 00FA
Description:
 JRSAFGroupNoOMVS
 The current group does not have a GID defined in the OMVS segment.
 Action: Create an OMVS segment with a GID.

QED!

Chris Mason

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



Debugging TSO FTP command

2008-04-07 Thread David Day
When I execute the TSO FTP command either using ISPF option 6 or exiting ISPF 
entirely and entering FTP a the ready prompt, I get the following abend and 
error message.

CEE5101C During initialization, the callable service BPX1MSS failed. The system
return code was 000156 , the   
 reason code was 0B0C00FA . The application will be terminated.

Under ISPF option 6, I also get the following

IEA995I SYMPTOM DUMP OUTPUT
  USER COMPLETION CODE=4093 REASON CODE=0090   
 TIME=13.53.21  SEQ=00233  CPU=  ASID=003B 
 PSW AT TIME OF ERROR  078D1000   8009BEAA  ILC 2  INTC 0D 
   ACTIVE LOAD MODULE   ADDRESS=00099060  OFFSET=2E4A  
   NAME=CEEBINIT   
   DATA AT PSW  0009BEA4 - 00181610  0A0D47F0  B10A1811
   GR 0: 8400   1: 84000FFD
  2: 0090   3: 0001
  4: 1177A350   5: 1177A160
  6: 11773080   7: 117734F8
  8:    9: 045BF406
  A: 0004   B: 8009BDD8
  C: 117747D0   D: 1177A030
  E:    F: 0090
 END OF SYMPTOM DUMP 

TCPIP address space is up and executing, and I can ping the mainframe from 
my PC.

What component owns CEE5101C?  I haven't had any luck finding it in any 
manuals, so far.  Any help would be appreciated. 

Thanks,

Dave Day 
   

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html




Re: Debugging TSO FTP command

2008-04-07 Thread McKown, John
 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:[EMAIL PROTECTED] On Behalf Of David Day
 Sent: Monday, April 07, 2008 2:19 PM
 To: IBM-MAIN@BAMA.UA.EDU
 Subject: Debugging TSO FTP command
 
 
 When I execute the TSO FTP command either using ISPF option 6 
 or exiting ISPF entirely and entering FTP a the ready prompt, 
 I get the following abend and error message.
 
 CEE5101C During initialization, the callable service BPX1MSS 
 failed. The system
 return code was 000156 , the  
  
  reason code was 0B0C00FA . The application will be 
 terminated.
 

[snip]

 
 Thanks,
 
 Dave Day 

The key is the 0B0C00FA, for which BPXMTEXT displays:

BPXPRIN1 03/08/07,
JRSAFGroupNoOMVS: The current group does not have a GID defined in the
OMVS segment.
Action: Create an OMVS segment with a GID.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

The information contained in this e-mail message may be privileged
and/or confidential.  It is for intended addressee(s) only.  If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense.  If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



Re: Debugging TSO FTP command

2008-04-07 Thread Ted MacNEIL
What component owns CEE5101C?

CEE is the prefix for LE.
And, the module abending under ISPF is an initialisation routine for LE.

Do you have LE in the link list?
-
Too busy driving to stop for gas!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



Re: Debugging TSO FTP command

2008-04-07 Thread David Day

John,
   Thanks.  I tried it using logonid IBMUSER and it took me straight in.  I 
just have to figure out now how to set my normal userid with the proper 
attributes.


   --Dave Day


- Original Message - 
From: McKown, John [EMAIL PROTECTED]

Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Monday, April 07, 2008 2:22 PM
Subject: Re: Debugging TSO FTP command



-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of David Day
Sent: Monday, April 07, 2008 2:19 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Debugging TSO FTP command


When I execute the TSO FTP command either using ISPF option 6
or exiting ISPF entirely and entering FTP a the ready prompt,
I get the following abend and error message.

CEE5101C During initialization, the callable service BPX1MSS
failed. The system
return code was 000156 , the

 reason code was 0B0C00FA . The application will be
terminated.



[snip]



Thanks,

Dave Day


The key is the 0B0C00FA, for which BPXMTEXT displays:

BPXPRIN1 03/08/07,
JRSAFGroupNoOMVS: The current group does not have a GID defined in the
OMVS segment.
Action: Create an OMVS segment with a GID.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

The information contained in this e-mail message may be privileged
and/or confidential.  It is for intended addressee(s) only.  If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense.  If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



Re: Debugging TSO FTP command

2008-04-07 Thread McKown, John
 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:[EMAIL PROTECTED] On Behalf Of David Day
 Sent: Monday, April 07, 2008 2:53 PM
 To: IBM-MAIN@BAMA.UA.EDU
 Subject: Re: Debugging TSO FTP command
 
 
 John,
 Thanks.  I tried it using logonid IBMUSER and it took me 
 straight in.  I 
 just have to figure out now how to set my normal userid with 
 the proper 
 attributes.
 
 --Dave Day

It is not your RACF id. It is your RACF default group which needs an
OMVS segment added to it.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

The information contained in this e-mail message may be privileged
and/or confidential.  It is for intended addressee(s) only.  If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense.  If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



Re: Debugging TSO FTP command

2008-04-07 Thread David Day
Thanks again John.  I added an OMVS segment to the group my userid is 
associated with and a GID(1) to the segment, and I now have access to FTP 
from the ISPF option 6 command line.


   -Dave Day
- Original Message - 
From: McKown, John [EMAIL PROTECTED]

Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Monday, April 07, 2008 3:03 PM
Subject: Re: Debugging TSO FTP command



-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of David Day
Sent: Monday, April 07, 2008 2:53 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Debugging TSO FTP command


John,
Thanks.  I tried it using logonid IBMUSER and it took me
straight in.  I
just have to figure out now how to set my normal userid with
the proper
attributes.

--Dave Day


It is not your RACF id. It is your RACF default group which needs an
OMVS segment added to it.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

The information contained in this e-mail message may be privileged
and/or confidential.  It is for intended addressee(s) only.  If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense.  If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



Re: Debugging TSO FTP command

2008-04-07 Thread Tony Harminc
2008/4/7 McKown, John [EMAIL PROTECTED]:

   CEE5101C During initialization, the callable service BPX1MSS
   failed. The system return code was 000156 , the
   reason code was 0B0C00FA . The application will be terminated.

  The key is the 0B0C00FA, for which BPXMTEXT displays:

  BPXPRIN1 03/08/07, JRSAFGroupNoOMVS: The current group does not have a GID 
 defined in the OMVS segment.
  Action: Create an OMVS segment with a GID.

And of course it is impossible to retrieve the text of this message
using the magic pfsctl() that BPXMTEXT uses, because the message
retrieval service will fail with exactly the same return and reason
codes!

In our code we have the known handful of such reason codes hardcoded
with their messages texts.  Sigh...

Tony H.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html