ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddp_5.4.0.1/rbal1psrf.htm

64 lines
5.0 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="reference" />
<meta name="DC.Title" content="Handle program start request failures for APPC" />
<meta name="abstract" content="When a program start request is received by an i5/OS subsystem on the application server (AS), the server attempts to start a job based on the information sent with the program start request. The application requester (AR) user's authority to the application server (AS), existence of the requested database, and many other items are checked." />
<meta name="description" content="When a program start request is received by an i5/OS subsystem on the application server (AS), the server attempts to start a job based on the information sent with the program start request. The application requester (AR) user's authority to the application server (AS), existence of the requested database, and many other items are checked." />
<meta name="DC.subject" content="problem handling, program start request failure, connection problems, program start request failure, message, application requester, program start request failure message, application server" />
<meta name="keywords" content="problem handling, program start request failure, connection problems, program start request failure, message, application requester, program start request failure message, application server" />
<meta name="DC.Relation" scheme="URI" content="rbal1wwu.htm" />
<meta name="DC.Relation" scheme="URI" content="../books/sc415442.pdf" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbal1psrf" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Handle program start request failures for APPC</title>
</head>
<body id="rbal1psrf"><a name="rbal1psrf"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Handle program start request failures for APPC</h1>
<div><p>When a program start request is received by an <span class="keyword">i5/OS™</span> subsystem
on the application server (AS), the server attempts to start a job based on
the information sent with the program start request. The application requester
(AR) user's authority to the application server (AS), existence of the requested
database, and many other items are checked.</p>
<div class="section"><p>If the AS subsystem determines that it cannot start the job (for
example, the user profile does not exist on the AS, the user profile exists
but is disabled, or the user is not properly authorized to the requested objects
on the AS), the subsystem sends a message, CPF1269, to the QSYSMSG message
queue (or QSYSOPR when QSYSMSG does not exist). The CPF1269 message contains
two reason codes (one of the reason codes might be zero, which can be ignored).</p>
</div>
<div class="section"><p>The nonzero reason code gives the reason why the
program start request was rejected. Because the remote job was to have started
on the AS, the message and reason codes are provided on the application server,
and not the application requester. The user at the AR only knows that the
program start request failed, not why it failed. The user on the AR must either
talk to the system operator at the AS, or use display station pass-through
to the AS to determine the reason why the request failed.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1wwu.htm" title="Investigating a problem usually begins with the user. Users might not be getting the results they expect when running a program or they might get a message indicating a problem. Sometimes the best way to diagnose and solve a problem is to go through the procedure with a user.">Work with distributed relational database users</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../books/sc415442.pdf " target="_blank">ICF Programming PDF</a></div>
</div>
</div>
</body>
</html>