Data Queue APIs--Categories - FTP Directory Listing - IBM
Data Queue APIs--Categories - FTP Directory Listing - IBM Data Queue APIs--Categories - FTP Directory Listing - IBM
Send Data Queue (QSNDDTAQ) API Send Data Queue (QSNDDTAQ) API Required Parameter Group: 1 Data queue name Input Char(10) 2 Library name Input Char(10) 3 Length of data Input Packed(5,0) 4 Data Input Char(*) Optional Parameter Group 1: 5 Length of key data Input Packed(3,0) 6 Key data Input Char(*) Optional Parameter Group 2: 7 Asynchronous request Input Char(10) Threadsafe: Conditional; see Usage Notes. The Send Data Queue (QSNDDTAQ) API sends data to the specified data queue. When an entry is sent to a standard data queue, the storage allocated for each entry will be the value specified for the maximum entry length on the Create Data Queue (CRTDTAQ) command. Distributed data management (DDM) data queues are supported using this API. This means that you can use this API to send data to a data queue that exists on a remote AS/400. Authorities and Locks Data Queue Authority *OBJOPR and *ADD Data Queue Library Authority *EXECUTE Data Queue Lock *EXCLRD http://infocntr.rchland.ibm.com/pubs/html/as400/v4r5/ic2924/info/apis/qsnddtaq.htm (1 of 5) [10/4/1999 2:32:39 PM]
Send Data Queue (QSNDDTAQ) API Required Parameter Group Data queue name INPUT; CHAR(10) The name of the data queue to send the data to. Library name INPUT; CHAR(10) The name of the library where the data queue resides. You can use these special values for the library name: *LIBL The library list *CURLIB The job's current library. Note: To improve data queue performance, the data queue APIs remember addressing information for the last data queues used. This occurs when a specific (not *LIBL or *CURLIB) value is provided for the library name. Because the addressing information is saved, users of this API should be aware of the following scenarios. Scenario 1 If, ❍ ❍ ❍ then, ❍ Scenario 2 If, ❍ ❍ ❍ then, a job references a library-specific data queue, the data queue is moved using the Move Object (MOVOBJ) command or renamed using the Rename Object (RNMOBJ) command, and a new data queue is created with the same name and library as the data queue that was renamed or moved, the job continues to reference the original data queue, not the newly created data queue. a job references a library-specific distributed data management (DDM) data queue, the DDM data queue is moved using the Move Object (MOVOBJ) command or renamed using the Rename Object (RNMOBJ) command, and a new data queue is created with the same name and library as the DDM data queue that was renamed or moved, http://infocntr.rchland.ibm.com/pubs/html/as400/v4r5/ic2924/info/apis/qsnddtaq.htm (2 of 5) [10/4/1999 2:32:39 PM]
- Page 1 and 2: Data Queue APIs--Categories Object
- Page 3 and 4: Data Queue APIs ● Send to a Data
- Page 5 and 6: Clear Data Queue (QCLRDTAQ) API Req
- Page 7 and 8: Clear Data Queue (QCLRDTAQ) API An
- Page 9 and 10: Receive Data Queue (QRCVDTAQ) API u
- Page 11 and 12: Receive Data Queue (QRCVDTAQ) API A
- Page 13 and 14: Receive Data Queue (QRCVDTAQ) API S
- Page 15 and 16: Receive Data Queue (QRCVDTAQ) API C
- Page 17 and 18: Retrieve Data Queue Description (QM
- Page 19 and 20: Retrieve Data Queue Description (QM
- Page 21 and 22: Retrieve Data Queue Description (QM
- Page 23 and 24: Retrieve Data Queue Description (QM
- Page 25 and 26: Retrieve Data Queue Message (QMHRDQ
- Page 27 and 28: Retrieve Data Queue Message (QMHRDQ
- Page 29 and 30: Retrieve Data Queue Message (QMHRDQ
- Page 31: Retrieve Data Queue Message (QMHRDQ
- Page 35 and 36: Send Data Queue (QSNDDTAQ) API INPU
- Page 37 and 38: User Queue APIs User Queue APIs Thi
- Page 39 and 40: Create User Queue (QUSCRTUQ) API To
- Page 41 and 42: Create User Queue (QUSCRTUQ) API Au
- Page 43 and 44: Create User Queue (QUSCRTUQ) API Do
- Page 45 and 46: Create User Queue (QUSCRTUQ) API Ex
- Page 47 and 48: Delete User Queue (QUSDLTUQ) API De
- Page 49 and 50: Delete User Queue (QUSDLTUQ) API CP
- Page 51 and 52: User Index APIs For details about M
- Page 53 and 54: Add User Index Entries (QUSADDUI) A
- Page 55 and 56: Add User Index Entries (QUSADDUI) A
- Page 57 and 58: Add User Index Entries (QUSADDUI) A
- Page 59 and 60: Create User Index (QUSCRTUI) API Mo
- Page 61 and 62: Create User Index (QUSCRTUI) API IN
- Page 63 and 64: Create User Index (QUSCRTUI) API Op
- Page 65 and 66: Create User Index (QUSCRTUI) API Se
- Page 67 and 68: Create User Index (QUSCRTUI) API ht
- Page 69 and 70: Delete User Index (QUSDLTUI) API Al
- Page 71 and 72: Remove User Index Entries (QUSRMVUI
- Page 73 and 74: Remove User Index Entries (QUSRMVUI
- Page 75 and 76: Remove User Index Entries (QUSRMVUI
- Page 77 and 78: Remove User Index Entries (QUSRMVUI
- Page 79 and 80: Retrieve User Index Attributes (QUS
- Page 81 and 82: Retrieve User Index Attributes (QUS
Send <strong>Data</strong> <strong>Queue</strong> (QSNDDTAQ) API<br />
Required Parameter Group<br />
<strong>Data</strong> queue name<br />
INPUT; CHAR(10)<br />
The name of the data queue to send the data to.<br />
Library name<br />
INPUT; CHAR(10)<br />
The name of the library where the data queue resides.<br />
You can use these special values for the library name:<br />
*LIBL<br />
The library list<br />
*CURLIB<br />
The job's current library.<br />
Note: To improve data queue performance, the data queue <strong>APIs</strong> remember addressing information<br />
for the last data queues used. This occurs when a specific (not *LIBL or *CURLIB) value is<br />
provided for the library name.<br />
Because the addressing information is saved, users of this API should be aware of the following<br />
scenarios.<br />
Scenario 1<br />
If,<br />
❍<br />
❍<br />
❍<br />
then,<br />
❍<br />
Scenario 2<br />
If,<br />
❍<br />
❍<br />
❍<br />
then,<br />
a job references a library-specific data queue,<br />
the data queue is moved using the Move Object (MOVOBJ) command or renamed using the<br />
Rename Object (RNMOBJ) command, and<br />
a new data queue is created with the same name and library as the data queue that was<br />
renamed or moved,<br />
the job continues to reference the original data queue, not the newly created data queue.<br />
a job references a library-specific distributed data management (DDM) data queue,<br />
the DDM data queue is moved using the Move Object (MOVOBJ) command or renamed<br />
using the Rename Object (RNMOBJ) command, and<br />
a new data queue is created with the same name and library as the DDM data queue that was<br />
renamed or moved,<br />
http://infocntr.rchland.ibm.com/pubs/html/as400/v4r5/ic2924/info/apis/qsnddtaq.htm (2 of 5) [10/4/1999 2:32:39 PM]