Article View: bit.listserv.asm370
Article #100Re: S0F8-10 error
From: Binyamin Dissen
Date: Mon, 26 Sep 2005 19:04
Date: Mon, 26 Sep 2005 19:04
79 lines
4452 bytes
4452 bytes
On Mon, 26 Sep 2005 14:12:53 -0400 Ing Usar <inguser2005@YAHOO.COM> wrote: :>On Mon, 26 Sep 2005 20:43:30 +0300, Binyamin Dissen :><bdissen@dissensoftware.com> wrote: :>>On Mon, 26 Sep 2005 12:44:02 -0400 Ing Usar <inguser2005@YAHOO.COM> wrote: :>>:>One other problem - I am getting an 0C4-11 when calling one of the services :>>:>in SP. Apparently the SP just waits by calling a WAIT macro (It doesn't :>>:>expect the client to POST it - so waits endlessly). :>> :>>Not too bright - check out the COMM ECB. :>Ing#### Question I have is is there any harm in letting the SP thread WAIT :>endlessly if it has nothing else to do (at least for now) after :>establishing the CMS environment. Won't the client when it calls a PC run :>on its own TCB? Always a good idea to allow the job to terminate cleanly. :>>:> Also the services are :>>:>not LOADed but is loaded into LPA. Could this be the reason for this abend? :>>Could be. :>Ing#### I tried placing this in LPA and fix it dynamically thru setprog. But :>still the same result. So are the services typically loaded ? Typically no need to place the services in common (may be different running on real old ESA hardware). :>>What is it referencing? What addressing mode? :>Ing##### Amode 31. The service I have currently does nothing as I am still :>trying to establish this connectivity from client to server and back. So all :>it does is BAKR & PR Look at the 0C4 information - it will tell you a bit. Look at the PSW and at what is being referenced. As a side point, your statement above indicates a bug. :>>:>Or do I need to explicitly make it non-swappable? :>>It would be a good idea. :>Ing##### Should I make both the SP and the services fixed in memory in :>addition to making the SP address space non-swappable? The service A/S must be swapped in when the service is invoked. The code itself need not (unless it is invoked by some service running in a state that cannot tolerate page faults). :>>:>Typically how are the service providers designed while waiting for a request :>>:>to come? Do they just execute WAIT ? :>>Depends on what else they do. :>>Why are you building this? Is it just practice, or do you have a use? :>Ing##### We have a need to consolidate a bunch of services callable from a :>few other address spaces. This is being done mostly to ease the maintenance Have you considered how to update them on a running system? Or that a failure in one can affect all of them? -- Binyamin Dissen <bdissen@dissensoftware.com> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies.
Technical Details
Message-ID:
<acggj1h0qjf6e1epq1rgo7pm9rs0kvs11g@4ax.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!sn-xit-02!sn-xit-06!sn-xit-01!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!dissensoftware.com!bdissenReferences:
<200509261812.j8QHQYtX007649@malibu.cc.uga.edu>Show Full Headers
Complete Article Headers
X-Google-Thread: fcdcb,c0d6f3d0dac0f7ef X-Google-Attributes: gidfcdcb,public X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!sn-xit-02!sn-xit-06!sn-xit-01!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!dissensoftware.com!bdissen From: Binyamin Dissen <bdissen@dissensoftware.com> Newsgroups: bit.listserv.asm370 Subject: Re: S0F8-10 error Date: Mon, 26 Sep 2005 22:04:52 +0300 Organization: DISSEN Software, Bar & Grill - Israel Ltd. Lines: 79 Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Message-ID: <acggj1h0qjf6e1epq1rgo7pm9rs0kvs11g@4ax.com> References: <200509261812.j8QHQYtX007649@malibu.cc.uga.edu> NNTP-Posting-Host: mozart.unx.sas.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: foggy.unx.sas.com 1127762374 20437 10.19.150.41 (26 Sep 2005 19:19:34 GMT) X-Complaints-To: usenet@unx.sas.com NNTP-Posting-Date: Mon, 26 Sep 2005 19:19:34 +0000 (UTC) Comments: Gated by NETNEWS@VM.SAS.COM Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU> X-Mailer: Forte Agent 2.0/32.652 Approved-By: Binyamin Dissen <bdissen@DISSENSOFTWARE.COM> In-Reply-To: <200509261812.j8QHQYtX007649@malibu.cc.uga.edu> Return-Path: owner-assembler-list@LISTSERV.UGA.EDU X-OriginalArrivalTime: 26 Sep 2005 19:19:31.0986 (UTC) FILETIME=[38FA1720:01C5C2CF] Originator: daemon@mozart.unx.sas.com