Results for PLS_INTEGER


1 to 20 of 337 results. Prev  Next
Results per page:   20  | 40 | 60


Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

get_size (id IN PLS_INTEGER) RETURN PLS_INTEGERRetrieves the size of the map message. Raises exception ORA-24197 if the Java stored procedure throws an exception during execution or ORA-24198 if the operation ID is invalid.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

read_short (id IN PLS_INTEGER) RETURN PLS_INTEGERthe end of the stream has been reached. Because there is no short type in PL/SQL, PLS_INTEGER is used … to represent a BYTE. Although PL/SQL users get an PLS_INTEGER, they are guaranteed that the value is

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

prepare (id IN PLS_INTEGER) RETURN PLS_INTEGERTakes the byte array stored in aq$_jms_stream_message and decodes it as a Java object in the Java stored procedure. The result of the decoding is stored as a static variable in Jserv session memory. Parameter id is used to identify the slot where the Java object is stored in the Oracle Database JVM session memory. If id is , then a new slot is created for this PL/SQL object. Subsequent JMS operations

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

read_byte (id IN PLS_INTEGER) RETURN PLS_INTEGERReads and returns a byte value from the stream message. If the end of the message stream has been reached, then is returned. Because there is no BYTE type in PL/SQL, INT is used to represent a byte. Although PL/SQL users get an INT, they are guaranteed that the value is in the Java BYTE value range. If this value is issued with a write_byte function, then there will not be an out of range error.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

get_mode (id IN PLS_INTEGER) RETURN PLS_INTEGERReturns the current mode of this message. The return value is either SYS.dbms_aqjms.READ_ONLY or SYS. dbms_aqjms.WRITE_ONLY. Raises exception ORA-24197 if the Java stored procedure throws an exception during execution or ORA-24198 if the operation ID is invalid.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

write_short (id IN PLS_INTEGER, value IN PLS_INTEGER)Writes a short to the bytes message as two bytes, high byte first. Because there is no short type in PL/SQL, INT is used to represent a short. Raises exception ORA-24193 if the parameter value exceeds the valid range, ORA-24196 if the bytes message is in write-only mode, ORA-24197 if the Java stored procedure throws an exception during execution, or ORA-24198 if the operation ID is invalid.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

write_byte (id IN PLS_INTEGER, value IN PLS_INTEGER)Writes a byte to the bytes message. Because there is no BYTE type in PL/SQL, PLS_INTEGER is used to

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

prepare (id IN PLS_INTEGER) RETURN PLS_INTEGERTakes the byte array stored in aq$_jms_map_message and decodes it as a Java object in the Java stored procedure. The result of the decoding is stored as a static variable in Jserv session memory. Parameter id is used to identify the slot where the Java object is stored in the Oracle Database JVM session memory. If id is , then a new slot is created for this PL/SQL object. Subsequent JMS operations

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

read_unsigned_byte (id IN PLS_INTEGER) RETURN PLS_INTEGERReads an unsigned 8-bit number from the bytes message stream and returns the next byte from the bytes message stream, interpreted as an unsigned 8-bit number. Null is returned if the end of the stream has been reached. Raises exception ORA-24196 if the bytes message is in write-only mode, ORA-24197 if the Java stored procedure throws an exception during execution, or ORA-24198 if the operation ID

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

prepare (id IN PLS_INTEGER) RETURN PLS_INTEGERTakes the byte array stored in aq$_jms_bytes_message and decodes it as a Java object in the Java stored procedure. The result of the decoding is stored as a static variable in Jserv session memory. Parameter id is used to identify the slot where the Java object is stored in the Oracle Database JVM session memory. If id is , then a new slot is created for this PL/SQL object. Subsequent JMS operations

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

write_int (id IN PLS_INTEGER, value IN PLS_INTEGER)Writes an INT to the bytes message. Raises exception ORA-24196 if the bytes message is in write-only mode, ORA-24197 if the Java stored procedure throws an exception during execution, or ORA-24198 if the operation ID is invalid.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

write_int (id IN PLS_INTEGER, value IN PLS_INTEGER)Writes an INT to the stream message. Raises exceptions ORA-24196 if the stream message is in read-only mode, ORA-24197 if the Java stored procedure throws an exception during execution, or ORA-24198 if the operation ID is invalid.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

read_int (id IN PLS_INTEGER) RETURN PLS_INTEGERReads and returns an INT from the stream message. If the end of the message stream has been reached, then is returned. Raises exception ORA-24194 if the type conversion between the type of real value and the expected type is invalid, ORA-24196 if the stream message is in write-only mode, ORA-24197 if the Java stored procedure throws an exception during execution, or ORA-24198 if the operation ID

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

get_mode (id IN PLS_INTEGER) RETURN PLS_INTEGERReturns the current mode of this message. The return value is either SYS.dbms_jms.plsql.MESSAGE_ACCESS_READONLY or SYS.dbms_jms.plsql.MESSAGE_ACCESS_WRITEONLY. Raises exception ORA-24197 if the Java stored procedure throws an exception during execution or ORA-24198 if the operation ID is invalid.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

read_byte (id IN PLS_INTEGER) RETURN PLS_INTEGERPLS_INTEGER to represent a BYTE. Although PL/SQL users get a PLS_INTEGER, they are guaranteed that the

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

read_unsigned_short (id IN PLS_INTEGER) RETURN PLS_INTEGERReads an unsigned 16-bit number from the bytes message stream and returns the next two bytes from the bytes message stream, interpreted as an unsigned 16-bit integer. Null is returned if the end of the stream has been reached. Raises exception ORA-24196 if the bytes message is in write-only mode, ORA-24197 if the Java stored procedure throws an exception during execution, or ORA-24198 if the operation

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

read_short (id IN PLS_INTEGER) RETURN PLS_INTEGERReads and returns a short value from the stream message. If the end of the message stream has been reached, then is returned. Because there is no short type in PL/SQL, INT is used to represent a byte. Although PL/SQL users get an INT, they are guaranteed that the value is in the Java short value range. If this value is issued with a write_short function, then there will not be an out of range error.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

write_short (id IN PLS_INTEGER, value IN PLS_INTEGER)Writes a short to the stream message. Because there is no short type in PL/SQL, INT is used to represent a short. Raises exceptions ORA-24196 if the stream message is in read-only mode, ORA-24197 if the Java stored procedure throws an exception during execution, or ORA-24198 if the operation ID is invalid.

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

get_names id IN PLS_INTEGER, names OUT aq$_jms_namearray, offset IN PLS_INTEGER, length IN PLS_INTEGER…Retrieves a portion of the names within the map message. Because aq$_jms_namearray has a size as 1024 and each element is a VARCHAR(200), this function will return an error if either limits are exceeded during the retrieval. (This means there is no sense to put a length parameter greater than 1024.) The index of the names of a map messages begins from 0. Parameter offset is the offset from which to

Packages and Types Reference, 10g Release 1 (10.1)

173 JMS Types

flush (id IN PLS_INTEGER)Takes the static variable in Jserv and synchronizes the content back to the aq$_jms_bytes_message. This procedure will not affect the underlying access mode. This procedure raises ORA-24197 if the Java stored procedure throws an exception during execution or ORA-24198 if the operation ID is invalid.


Was this page helpful?