Search results for query: *

That's what I was afraid of. Looks like I'll have to find a less elegant solution to this problem. Thanks!

Ok. Follow-up on this. I found the problem with selecting from the temp table. I'd been attempting to do open p_cursor for select * from ipts_sd.corr_item_temp; When I should have been doing: open p_cursor for 'select * from ipts_sd.corr_item_temp'; The single quotes make it so that...

Well, that's the trick with this one. I need the temp tables to be different for every letter that is generated. So, I need a system where there can be multiple users with their own version of the temp table that will have different columns (and number of columns). Really, all I want is a local...

Well, that works just fine. Thanks! I'll have to play with it to see why my code isn't working properly. Anyone have any ideas on what I'm doing wrong?

...--dbms_output.put_line(v_insert); execute immediate v_insert; commit; open p_cursor for select * from ipts_sd.corr_item_temp; else open p_cursor for select null from dual; end if; END; All of that works, except that I can't...

Somewhere around 100.

Making the table transactional or just session based doesn't bother me. It'll get dropped eventually anyway, and I've got logic in to drop it if it exists anyway. I'll try to be a little more specific. The table that holds the letters looks like this Letter_ID Letter_Item_Label...

I need to do something that seems like it'd be easy, but I can't for the life of me figure out how to do this in oracle. We have a table that contains information about letters that contains (among others) the fields: Letter Id, Column_Nm and Column_Val. A given letter might have anywhere from...

You may want to try using the Spreadsheet::ParseExcel module from CPAN. It is specifically designed for dealing with excel, and I have always found it very easy to use.

You have a LOT of options. How big are your files going to be? If you are just trying to lots of small files that contain a single record, as it were, I would probably just read in each file one at a time (pass the program a list of files to read). Then, for each line, do a split on '='. Take...

Well, the test script that comes with the MVS::JESFTP package does that, so I sort of assume it is possible. I'll check out that website. Thanks!

That looks like it worked. I guess I need to just send in the JCL I want rather than calling the JCL that is already on the mainframe. Eh. Whatever works. Thanks chazoid!

Well, first thing I see is that the variable $output_file is not being set anywhere. You are trying to output to a null location.

...or die "not ok 4\n"; print "ok 4\n"; The SEQ file has this in it: //logonid1 JOB account,'HACGHH',CLASS=A,MSGCLASS=T,MSGLEVEL=(1,1) //*LOGONID HACGHH //*PASSWORD HACGHH19 /*ROUTE PRINT node.logonid //STEP001 EXEC PGM=IA000000.SW.LIB(SWRAPUP) Any ideas? Thanks!

Another way to deal with variables in the middle of a word is to to do something like this: src='${server}${celebid}1024x768.jpg'> which will let perl know what the variable names you are using are.

Your problem is that MLDBM does not support the standard multi-level perl hash structure. You have to create a temporary hash with the multi-level structure and then set the top level into your tied hash. Something like this: my %temp_users; $temp_users{$temp{$fh}}{'user'} = $temp{$fh}...

Date::Manip will do just about anything. It's not fast, though, so if you need speed you'd be better off using one of the other packages on CPAN. Date::Calc, for instance, is quite a bit faster for most applications. If you don't need speed, however, I've found that Date::Manip is great to have...

The books mentioned in that thread are really good, as is the Perl Black Book, which I find indespensible for actually solving problems. It is geared towards people who have a job to do and need a solution now, not tomorrow. ;)

While I don't know of any automatic ways to determine the length of a hash, you could write a quite subroutine to do so. my $hashcount = &GetHashCount(\%myHash); sub GetHashCount { my $hash_ref = shift; my $count = 0; foreach $key (keys $%hash_ref) { $count++...

If using 'my' on some of the variables fixed it, you probably had a locality problem. Were $horz and $vert populated somewhere else in the script before you tried to use them? Without seeing the whole script, my guess would be that something somewhere else was changing the values of $horz and...