141 lines
7.2 KiB
HTML
141 lines
7.2 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="SECURITY (Security) keyword for ICF files" />
|
||
|
|
<meta name="abstract" content="Use this file- and record-level keyword to include security information when your program starts a program on a remote system (see the EVOKE keyword)." />
|
||
|
|
<meta name="description" content="Use this file- and record-level keyword to include security information when your program starts a program on a remote system (see the EVOKE keyword)." />
|
||
|
|
<meta name="DC.subject" content="SECURITY (Security) keyword" />
|
||
|
|
<meta name="keywords" content="SECURITY (Security) keyword" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakemstckeyw.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="icfsecu" />
|
||
|
|
<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>ICF Files, SECURITY</title>
|
||
|
|
</head>
|
||
|
|
<body id="icfsecu"><a name="icfsecu"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">SECURITY (Security) keyword for ICF files</h1>
|
||
|
|
<div><p>Use this file- and record-level keyword to include security information
|
||
|
|
when your program starts a program on a remote system (see the EVOKE keyword).</p>
|
||
|
|
<div class="section"><p>Any record format that has the SECURITY keyword specified for
|
||
|
|
it or implied for it by being specified at the file level must have the EVOKE
|
||
|
|
keyword specified on that record format or implied for that record format
|
||
|
|
by being specified at the file level. If you do not specify the EVOKE keyword,
|
||
|
|
a severe error occurs and the file is not created.</p>
|
||
|
|
<div class="p">The format of the
|
||
|
|
keyword is: <pre>SECURITY(security-subfield subfield-definition[.3.])</pre>
|
||
|
|
</div>
|
||
|
|
<p>The
|
||
|
|
security-subfield parameter identifies the subfield being defined. This parameter
|
||
|
|
is required. The value specified must be one of the following values:</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr valign="bottom"><th valign="bottom" id="d0e33">Value</th>
|
||
|
|
<th valign="bottom" id="d0e35">Meaning</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e33 ">1</td>
|
||
|
|
<td valign="top" headers="d0e35 ">(Profile ID)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e33 ">2</td>
|
||
|
|
<td valign="top" headers="d0e35 ">(Password)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e33 ">3</td>
|
||
|
|
<td valign="top" headers="d0e35 ">(User ID)</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<p>The subfield-definition parameter must be one of the following
|
||
|
|
parameters. If you enter the password as literal (character string),
|
||
|
|
the characters are interpreted by the CCSID of the ICF file; otherwise, characters
|
||
|
|
are interpreted by the CCSID of the current job.</p>
|
||
|
|
<dl><dt class="dlterm">*USER</dt>
|
||
|
|
<dd>Indicates that the user profile name of the user should be used as the
|
||
|
|
value of the security subfield. For example, if *USER is specified for the
|
||
|
|
password subfield, the user profile name is used as the password.</dd>
|
||
|
|
<dt class="dlterm">*NONE</dt>
|
||
|
|
<dd>Indicates that a null security value should be used.</dd>
|
||
|
|
<dt class="dlterm">'character-string'</dt>
|
||
|
|
<dd>You can specify up to 128 single-byte characters for a password.</dd>
|
||
|
|
<dt class="dlterm">field-name</dt>
|
||
|
|
<dd>The specified field contains the security information. <p>The length of
|
||
|
|
the field can range from 1 to 10 bytes, or it may be 512 bytes. The number
|
||
|
|
of characters, as interpreted by the CCSID of the current job, cannot exceed
|
||
|
|
128. Values greater than 128 should only be used if multi-byte characters
|
||
|
|
are specified for the password. The default length of the field is 10 bytes.</p>
|
||
|
|
<p>This
|
||
|
|
parameter is not valid if you specify the SECURITY keyword at the file level.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">&field-name</dt>
|
||
|
|
<dd>The specified field contains the security information. <p>The length of
|
||
|
|
the field can range from 1 to 10 bytes, or it may be 512 bytes. The number
|
||
|
|
of characters, as interpreted by the CCSID of the current job, cannot exceed
|
||
|
|
128. Values greater than 128 should only be used if multi-byte characters
|
||
|
|
are specified for the password. The default length of the field is 10 bytes.</p>
|
||
|
|
<p>This
|
||
|
|
parameter is not valid if you specify the SECURITY keyword at the file level.</p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
<p>You cannot specify SECURITY with the TIMER keyword.</p>
|
||
|
|
<p>Option
|
||
|
|
indicators are valid for this keyword.</p>
|
||
|
|
</div>
|
||
|
|
<div class="example"><h4 class="sectiontitle">Example</h4> <p>The following example shows how to specify
|
||
|
|
the SECURITY keyword.</p>
|
||
|
|
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
|
||
|
|
00010A 01 SECURITY(2 'JONES' 3 'WHITE')
|
||
|
|
00020A
|
||
|
|
00030A
|
||
|
|
00040A
|
||
|
|
00050A
|
||
|
|
00060A R RCD1
|
||
|
|
00070A 03 SECURITY(2 'JONES' 3 *USER)
|
||
|
|
00080A EVOKE(LIB2/PGM2)
|
||
|
|
00090A
|
||
|
|
00100A R RCD2
|
||
|
|
00110A EVOKE(LIB3/PGM3)
|
||
|
|
00120A
|
||
|
|
00130A FIELD1 5A
|
||
|
|
00140A
|
||
|
|
00150A R RCD3
|
||
|
|
00160A 60 SECURITY(2 &CLVAR1 3 &CLVAR2);
|
||
|
|
00170A EVOKE(LIB4/PGM4)
|
||
|
|
00180A CLVAR1 10A
|
||
|
|
00190A CLVAR2 10A
|
||
|
|
A</pre>
|
||
|
|
<p>SECURITY specified at the file level applies to all formats
|
||
|
|
and if selected (indicator 01 is on), the password of JONES and user ID of
|
||
|
|
WHITE are sent to the remote system.</p>
|
||
|
|
<p>For RCD1, if indicator 03 is set
|
||
|
|
on, the user profile name of the current user is used as the user ID and is
|
||
|
|
sent with the password JONES as security information to the remote system.</p>
|
||
|
|
<p>For
|
||
|
|
RCD2, no security information is sent to the remote system.</p>
|
||
|
|
<p>For RCD3,
|
||
|
|
if indicator 60 is set on, the value contained in CLVAR1 is used as the password,
|
||
|
|
the value in CLVAR2 is used as the user ID, and both are sent as security
|
||
|
|
information to the remote system.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakemstckeyw.htm" title="These topics contain the keyword entries that you can specify when you define ICF files.">DDS keyword entries for ICF files (positions 45 through 80)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|