Oddly enough I had just found that article and used part of it's logic and part of another on skipping a task to do what I needed. 

In case anyone is...

Hmmm...but that is exactly what I did the first time and for some reason, while the task would execute fine and I had the output parameter mapped to global variable,...

Is there an advantage to that over what I have done?

Nevermind, got this to work finally!  I changed my stored procedure to this...

CREATE PROCEDURE sp_test(@paramater1 varchar(10), @parameter2 varchar(100), @new_id int OUTPUT)

AS

SET NOCOUNT ON

INSERT INTO tblName (value1, value2) VALUES (@paramater1 ,...

Sorry if I was unclear, but this already is in a stored procedure.  I tried what you mention, but unless I return a recordset (rather than just an output parameter)...