Well, they say if all you have is a hammer everything looks like a nail.
Try the same trick again.
Since INSERT is not a cursor you can use EXECUTE IMMEDIATE txt
DB2 supports INSERT INTO T VALUES (....), (.....)
for multi row insert.
Oh and remember ".." is for identifiers, '...' is for strings.

Cheers
Serge

PS: Gluing together statements on the fly and compiling them one of is
not DB2's preferred mode of operation.. It eats CPU, but it gets the job
done. Good learning experience any day.

Why do you have OIDs in SQL?  Why huge column sizes that invite bad
data? Why did you violate ISO-11179 naming rules?  How usable and
descriptive do you think that "data_field" is as a name?  Do you know
that a column and field are nothing alike?  What is "reason"?  A better
name would "vague_reason" for the guy who has to maintain it :)  Didyou
pick VARCHAR(256) after actuall research, or is it a "magic number"
that was easy write on the fly?

I do dnot know what DB2's limit on parameters is, but you can fake an
array in SQL/PSM, soemthing like this:

CREATE PROCEDURE AddLog
(IN player_oid_1 CHAR(36), -- OIDs in SQL?
IN play_time_1 CHAR(23), -- temporal data in string?
IN content_name_1 VARCHAR(1024), -- really that big?
IN content_oid_1 CHAR(36), -- OIDs in SQL?
IN vague_reason_1 VARCHAR(256), -- for what??
IN data_field_1 VARCHAR(256), -- fields in SQL? what kind of data

IN player_oid_2 CHAR(36),
IN play_time_2 CHAR(23),
IN content_name_2 VARCHAR(1024),
IN content_oid_2 CHAR(36),
IN vague_reason_2 VARCHAR(256),
IN data_field_2 VARCHAR(256),

etc.

IN player_oid_6 CHAR(36),
IN play_time_6 CHAR(23),
IN content_name_6 VARCHAR(1024),
IN content_oid_6 CHAR(36),
IN vague_reason_6 VARCHAR(256),
IN data_field_6 VARCHAR(256),

)
LANGUAGE SQL
BEGIN

INSERT INTO PlayLogs (player_oid, play_time, content_name,
content_oid, reason, data_field)
VALUES (player_oid_1, play_time_1, content_name_1, content_oid_1,
vague_reason_1, data_field_1);

--skip the insert if the data is missing
IF player_oid_2 IS NOT NULL
THEN
INSERT INTO PlayLogs (player_oid, play_time, content_name,
content_oid, reason, data_field)
VALUES (player_oid_2, play_time_2, content_name_2, content_oid_2,
vague_reason_2, data_field_2);
END IF;

etc.

IF player_oid_6 IS NOT NULL
THEN
INSERT INTO PlayLogs (player_oid, play_time, content_name,
content_oid, reason, data_field)
VALUES (player_oid_6, play_time_6, content_name_6, content_oid_6,
vague_reason_6, data_field_6);
END IF;

END;

The right answer is to split the data in the host program and make
calls the stored procedure, but you knew that from basic Software
Engineering and how a teired architecture works.

If your question is how to accept an unconstrained set of parameters,
the answer is db2 does not support that. However, db2 does allow
PROCEDURE overloading. That is, while the PROCEDURE must have a name,
more than one procedure with the same name (but not the same SPECIFIC
name) can be CREATEd, and each can be given a different set of
parameters. With that, you can CREATE a number of PROCEDUREs, each one
for each multiple of 6.

Ideally, however, this is not the best solution, and the PROCEDURE
should just INSERT one record at a time, and have it called one after
the other.

B.