lil bit bigger than small block
That be an all aluminum 427
Displacement at the small block weight
Enjoy the benefits of a premium membership!
Upgrade Account
-
TalkBass has been independent since 1998. Add your voice.
Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
Join free Log in
Want zero display ads or expanded classifieds tools? Compare plans.
Please explain the origin of your user name
- Thread starter dbase
- Start date
That be an all aluminum 427
Displacement at the small block weight
I thought that looked a little phat for a 327. Cool. What's it in?lil bit bigger than small block
That be an all aluminum 427
Displacement at the small block weight
Dontcha know!
the 327 part is the car engine though. and Mrb is my name. See that, back on topic
the 327 part is the car engine though. and Mrb is my name. See that, back on topic
s0c9
Supporting Member
I'm an IT guy.. S0C9 is a mainframe system error code.
-------------------------------------------------------------------------------------------------
A division gave a quotient which was too large for the program defined field.
Possible causes & Solution:
1. An attempt was made to divide by zero.
2. An attempt was made to divide by too small of a number.
3. A program loop containing an arithmetic instruction caused an invalid result.
4. A sort operation was missing a SORTIN or SORTOUT JCL DD card.
An error occurred in end-of-volume processing on a magnetic tape volume.
1. An error occurred in header or trailer label processing.
2. An error occurred in positioning the magnetic tape.
3. The recording medium was defective.
An I/O error occurred while writing a tapemark or an end-of-volume label.
An I/O error occurred while the tape was being positioned for label processing an I/O error occurred in reading the trailer label of an input or inout data set.
An I/O error occurred while positioning at the end of a magnetic tape volume.
An I/O error occurred in reading the header label for an input or inout data set.
An I/O error occurred while positioning for the first data record of a magnetic tape data set.
An invalid trailer label was encountered in end-of-volume processing.
An invalid header label was encountered in end-of-volume processing.
A specific vol=ser was specified for a multi-volume output data set.
One of the volumes contained a data set whose expiration date had not yet passed.
1. Resubmit the job specifying a different volume or device.
If this does not correct the problem, recreate the data set on a different volume or device.
Recreate the data set on a different volume or device.
For multi-volume data sets, be sure the labeling is consistent.
1. If the label format is incorrect, recreate the data set and resubmit the job.
2. If the label appears correct, specify a different volume or device.
If there is not a tapemark after the data, recreate the data set, specifying a different volume or device.
1. If the label format is incorrect, recreate the data set and resubmit the job.
2. If the label appears correct, specify a different volume or device.
3. For multi-volume data sets, recreate the data set, ensuring that the labeling is consistent.
1. Verify that the data on the data set appears correct. If so, specify a different volume or device, and recreate the data set.
2. If there is no data on the data set, recreate the data set, and resubmit the job.
1. If the trailer label is invalid, recreate the data set, and resubmit the job.
For multi-volume data sets, be sure that the labeling is consistent.
2. If the label appears correct, specify a different device.
If this does not correct the problem, recreate the data set on a different volume.
1. If the header label is invalid, recreate the data set, and resubmit the job.
For multi-volume data sets, be sure that the labeling is consistent.
2. If the label appears correct, specify a different device.
If this does not correct the problem, recreate the data set on a different volume.
If the correct volume was definitely specified, tell the operator that the volume is to be used even though the expiration date has not passed.
-------------------------------------------------------------------------------------------------
A division gave a quotient which was too large for the program defined field.
Possible causes & Solution:
1. An attempt was made to divide by zero.
2. An attempt was made to divide by too small of a number.
3. A program loop containing an arithmetic instruction caused an invalid result.
4. A sort operation was missing a SORTIN or SORTOUT JCL DD card.
An error occurred in end-of-volume processing on a magnetic tape volume.
1. An error occurred in header or trailer label processing.
2. An error occurred in positioning the magnetic tape.
3. The recording medium was defective.
An I/O error occurred while writing a tapemark or an end-of-volume label.
An I/O error occurred while the tape was being positioned for label processing an I/O error occurred in reading the trailer label of an input or inout data set.
An I/O error occurred while positioning at the end of a magnetic tape volume.
An I/O error occurred in reading the header label for an input or inout data set.
An I/O error occurred while positioning for the first data record of a magnetic tape data set.
An invalid trailer label was encountered in end-of-volume processing.
An invalid header label was encountered in end-of-volume processing.
A specific vol=ser was specified for a multi-volume output data set.
One of the volumes contained a data set whose expiration date had not yet passed.
1. Resubmit the job specifying a different volume or device.
If this does not correct the problem, recreate the data set on a different volume or device.
Recreate the data set on a different volume or device.
For multi-volume data sets, be sure the labeling is consistent.
1. If the label format is incorrect, recreate the data set and resubmit the job.
2. If the label appears correct, specify a different volume or device.
If there is not a tapemark after the data, recreate the data set, specifying a different volume or device.
1. If the label format is incorrect, recreate the data set and resubmit the job.
2. If the label appears correct, specify a different volume or device.
3. For multi-volume data sets, recreate the data set, ensuring that the labeling is consistent.
1. Verify that the data on the data set appears correct. If so, specify a different volume or device, and recreate the data set.
2. If there is no data on the data set, recreate the data set, and resubmit the job.
1. If the trailer label is invalid, recreate the data set, and resubmit the job.
For multi-volume data sets, be sure that the labeling is consistent.
2. If the label appears correct, specify a different device.
If this does not correct the problem, recreate the data set on a different volume.
1. If the header label is invalid, recreate the data set, and resubmit the job.
For multi-volume data sets, be sure that the labeling is consistent.
2. If the label appears correct, specify a different device.
If this does not correct the problem, recreate the data set on a different volume.
If the correct volume was definitely specified, tell the operator that the volume is to be used even though the expiration date has not passed.
s0c9
Supporting Member
Yes, but is your trailer label valid? LOL?
The gain knob on my amp works
Nickname from an old girlfriend about 20 years ago. Others took to it and numbers have some sports angle to them.
I had an english teacher who was from spain.
After a reading exercise he had a pop quiz.
He meant to ask me:
"Bengt, what do you think about the mother-in-law".
But what he said was:
"Baa, vat du ju sink abut zhe mosser-in-lau?"
After that i've been stuck with that nick.
Then there's the bass clef (for obvious reasons)
And blue/yellow colors because i'm swedish.
I have my "logo" tatooed on my calf
After a reading exercise he had a pop quiz.
He meant to ask me:
"Bengt, what do you think about the mother-in-law".
But what he said was:
"Baa, vat du ju sink abut zhe mosser-in-lau?"
After that i've been stuck with that nick.
Then there's the bass clef (for obvious reasons)
And blue/yellow colors because i'm swedish.
I have my "logo" tatooed on my calf
Wow, I haven't seen Job Control Language when submitting code to be compiled since 1974... I cant believe I still remember this stuff.
These things seem to happen to me a lot.
Urban Dictionary says:
When good intentions go bad, messily.
History: From LCDR Charles Breen, USN, who tried to untangle a goat's rope, only to be bitten by said goat, then to deck same goat, Mongo style, right as busload of tourists rounded the bend in time to think he was beating the crap out of a goat for no reason. This definition dates back to at least 1988.
Example:
Man, this is the last time I help you move, what a goat rope.
Urban Dictionary says:
When good intentions go bad, messily.
History: From LCDR Charles Breen, USN, who tried to untangle a goat's rope, only to be bitten by said goat, then to deck same goat, Mongo style, right as busload of tourists rounded the bend in time to think he was beating the crap out of a goat for no reason. This definition dates back to at least 1988.
Example:
Man, this is the last time I help you move, what a goat rope.
I was born in 1951. The Fender Bass was born in 1951. I'm a "dude" that plays bass. The '51 P Bass is my all time favorite bass!
bassdude51
bassdude51
